Re: cygwin-xfree

[Jason Molenda <jason-swarelist@molenda.com>]

On Wed, May 03, 2000 at 10:18:05PM -0400, Chris Faylor wrote:

> 1) What does everyone think about adding another 150MB to the server.  There
>    seems to be more than adequate disk space available for this but 150MB
>    is still a pretty massive project.  I can just imagine what will happen
>    to sourceware the first time someone checks this out.


IMHO 150MB isn't very much - I way overspec'ed the CVS drive so
there is a lot of slack there.

(On the other hand, the web drive and the htdig drive are filling
at a rate faster than I had anticipated and won't last the ~18 month
lifetime I had intended for this system :-(


> 2) I assume that if you all think that 1) is no problem then this directory
>    should be winsup/xfree.  

It almost seems like something you'd want to put in a separate
repository.  I mean, it's _really_ Xfree86 with a few patches on
top (OK, a lot of patches).  How would you handle e.g. make or perl
(I'm trying to guess at programs that might have cygwin patches to
them) if someone wanted to do the same?


> The winsup directory is not being mirrored by any of the CVS mirrors, right?

If anyone is rsync'ing the entire src repository, they'll pick it
up, but it's not the end of the world for them to end up with
another ~150MB.  I would think about it more like "Where do I want
third party programs that we maintain patches to be checked in?"

Maybe a new repository, "cygwin-mods" or something, would be the cleanest
approach.  But cygwin-mods is a terrible name.


If he ever does get ready to start importing Xfree86, please make sure
he reads the CVS manual on tracking third party sources,
	http://www.loria.fr/~molli/cvs/doc/cvs_13.html#SEC98

or provide exact command lines for him.  It'd probably make sense
to import the most recent release of xfree86, then the development
version on which he's based his changes, and then check in his
changes on top of that.

That way if he dies in a tragic pingpong ball manufacturing plant accident,
people will be able to disentangle what he was up to.  It's really
easy to import sources incorrectly, and annoying to recover from that
at a later date.



> I'm have mixed feelings about this.  If we can't provide this, the developer
> will go to Source Forge.  

I don't have a strong opinion either, I did want to interject some
facts about the system and stuff, tho.



J