From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Faylor To: Jason Molenda Cc: overseers@sourceware.cygnus.com Subject: Re: cygwin-xfree Date: Wed, 03 May 2000 19:53:00 -0000 Message-ID: <20000503225326.A13697@cygnus.com> References: <20000503221805.A13179@cygnus.com> <20000503194427.A27318@shell17.ba.best.com> X-SW-Source: 2000-q2/msg00147.html Message-ID: <20000503195300.mjWG5USfEft8n55xg8LKtfxtS0X37jzzTI_WVOwu6sA@z> On Wed, May 03, 2000 at 07:44:27PM -0700, Jason Molenda wrote: >> 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? Dunno. I've been thinking that the winsup directory should be its own little mini-build tree. I didn't want to pollute the rest of sourceware with stuff that was only intended for cygwin. >> 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. Maybe cygwin-apps? >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. Yup. I supplied the exact command lines for him. And emphasized repeatedly that he follow them exactly. And he screwed them up... >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've repeatedly stressed this to him. He spent all last night checking everything in but somehow it never showed up on sourceware, or, at least I can't find it. He says that he understands why this happened. >>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. Thanks, Jason. cgf