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.
> You can create packages on sourceforge
^^^^^^^^^^^^^^^
That is I am asking for. Everyone says, that's easy to do - even the
docs - but not HOW to do this.
> and then release some files as a specific version of that
> package. That's totally unrelated from importing a cvs tree
> (which is what Jon was asking about). Did anybody actually read
> this link:
>
> http://sourceforge.net/docman/display_doc.php?docid=768&group_id=1
Yes. The import issue is not the real mess for me...
> I ask again: what is holding you up from setting up the cvs tree
> on sourceforge ? I understand that you want to refactor the
> source tree somewhat while you are at it, but this point was
> already discussed three months ago, and nothing happened. What
> are you waiting for ??
See above.
CU,
Christoph Egger
E-Mail: [EMAIL PROTECTED]
