Hi, I don't have a deep knowledge of CVS and I haven't used sourceforge at all but maybe I can say something that might interest you. Sorry if I misunderstood the sourceforge issue. Christoph Egger wrote: > > On Wed, 21 Mar 2001, Stefan Seefeld wrote: > > > Christoph Egger wrote: > > > > > On Tue, 20 Mar 2001, Jon M. Taylor wrote: > > > > > >> There's nothing checked in to the SourceForge CVS tree, and we > > >> have no more cvs.ggi-project.org. What's the holdup on comitting the > > >> degas/ tree to SourceForge CVS? > > > > > > > > > Nothing will happen there as long as no one creates file-packages for > > > each extension. I don't know, HOW this can be done there... > > > > > > Does anyone know that? > > > > I don't understand what a cvs tree and a file-package have to do > > with each other. > > Maintainance. file-packages are represented as a TOP-DIRECTORY in > cvs. Not necessarily. You can create packages that are aliases to sub-directories. Just edit CVSROOT/modules and put a line like "mymodule -a topdir/subdir". When retrieving mymodule, you will get topdir/subdir ans not a toplevel directory named mymodule. Note that CVSROOT can be maintained remotely with CVS as well (no need to ssh on sourceforge in order to edit it). Xavier
