GlobalLIFE CVS

1
GlobalLIFE CVS

• How-to use it

2
Setting UP CVS

• Server Side. Up Running
• Each GlobalLIFE Developer gets an unique account
• Just for CVS not ssh
• Anonymous access
• Read only
• Authentification throught pserver
• Users creation script on-line
• http//globallife.informatik.uni-bremen.de/cgi-bin
  /cvspass.cgi

3
Client Side

• Choose CVS client
• Plattform independent
• WinCVS, CVSgui, MacCVS, SmartCVS, jCVS
• CVSin. Plug-in for MS visual C
• viewCVS. Web access.
• Client example(TortoiseCVS)
• Windows Explorer pulg-in
• You can expand the columns shown in the Windows
  Explorer window and sort by status, review
  versions and more
• recursively update or commit everything
• Basic, Easy to use and enough
• http//www.tzi.de/mamama/globalLife/cvs/TortoiseC
  VS-1-2-2.exe

4
Setting up the Client

• Each GL developer should use his account
• TortoiseCVS configuration
• Protocol pserver
• Server globallife.informatik.uni-bremen.de
• Port 2401
• Repository Dir. /home/cvsuser/glCVS
• User Name account you created via
  cvsuser-script
• Module concepts, source code (event. More)
• First time password will be asked

5
TortoiseCVS configuration snapshot
6
Getting started. A real-life Example

• Choose a local folder for the working copy of
  the GL CVS repository
• On the folder. Right-mouse button
• CVSCheckout. Make a copy of the GL repository on
  your local Dir.
• You check-out ONLY the module you select
• Repeat check-out for all existing modules
• Source code and concepts
• We can start to work out the project files.

7
Typical / Common CVS operations

• Update.
• Before we want to start manipulating files we
  should ALWAYS make Update.
• Open a explorer window for some of the modules
  and with right-mouse button press Update
• If file icon color-layout is green, then file is
  up-to-date
• Add new contents. (files or directories)
• If we created new files inside some module or
  module subfolder, we should add them to the CVS
  repositoty.
• Add contents doesnt mean COMMIT.
• Other user wont see your changes until you
  commit them
• If the icon has a question-sign over, it must be
  added.

8
Typical / Common CVS operations (cont.)

• Commit.
• Adds permanently the files or dir. to the
  repository
• After you have added new files or directories,
  you should commit them in order to enable other
  GL members to see the new files
• After modified a file (icon-color from green to
  red), you also should commit it.
• If the file icon-layout color is red, it means
  that the file has not still been commited.

9
Typical / Common CVS operations (cont.)

• History
• It shows the several versions of a file (Rev_id,
  how, when, comments
• We can recover a concrete file revision
• We can check the differences between several
  versions
• Required diff application. EX. Examdiff
• Web Log
• The same information that via History, but enable
  us to use viewcvs.cgi.
• A web interface for access the CVS repository.
  Not yet installed.
• Revision Graph.
• Just a graphical view of the history

10
Typical / Common CVS operations (cont.)

• Remove
• Remove a file from the repository
• If deleted directly (explorer), repository will
  not change. Next Update you get the file again.
• After remove it you must make commit in order
  to remove it permanently.

11
Web Resources

• http//www.cvshome.org/
• The Home of CVS
• http//cvsbook.red-bean.com/
• Documentation Open source development with CVS
• http//www.wincvs.org/
• A windows CVS GUI
• http//www.tortoisecvs.org/
• A CVS GUI for windows (Explorer pug-in)