state of wx_port layout

[Bruno Postle]

On Wed 16-Apr-2003 at 12:42:49PM +0200, Kai-Uwe Behrmann wrote:
> 
> I forgot to ask You
> did You find an gui for cvs usefull?

I've never used one, though they are probably quite good when a
project has lots of branches, it does get very hard to visualise
what is going on.

A lot of projects don't need branches, in which case all you ever
need are a few command-lines:

cvs checkout ...  # for getting a fresh source tree

cvs update        # pull other peoples changes from the server

cvs add ...       # prepare a new file/directory for uploading

cvs commit        # commit local changes to the server

cvs tag ...       # label a 'moment in time' for later reference

Things get more complex with branches, the best plan is to try and
maintain a 'trunk' that has the most stable code and which always
compiles.

Small short lived branches can be used for developing extra
features; when the feature is finished, it can be merged 'back to
the trunk' and the branch is then abandoned.

For your wx-ptopengui project on sourceforge, you should be aware of
the drawbacks of cvs before you do the initial import:

o  You can *not* rename files or directories, try to get them right
   the first time, otherwise you have to 'delete and add', which
   gets very boring and loses all the metadata.

   So before you decide on a directory structure, look at some other
   similar projects and see how they are organised.

o  You can *not* delete directories at all.  So think before you
   create one.

-- 
Bruno