[patch]: Decouple cygwin building from in-tree mingw/w32api building

Yaakov (Cygwin/X) yselkowitz@users.sourceforge.net
Sun Oct 21 18:32:00 GMT 2012

On Sun, 2012-10-21 at 13:10 -0400, Christopher Faylor wrote:
> That said, is it time to ask the mingw.org stuff to relocate their
> CVS repo?  I could tar up the affected CVS directories for them if
> so.

What about some CVSROOT/modules magic to exclude winsup/mingw and
winsup/w32api from a Cygwin checkout?  

1) change the existing cygwin module to naked-cygwin;
2) add a new cygwin module with "-a src-support naked-cygwin
naked-newlib naked-include";
3) change the directions on cvs.html to "cvs co cygwin" instead of "cvs
co winsup" for new checkouts;
4) devs with existing checkouts could just rm -fr winsup/mingw
winsup/w32api if they so choose (but with the patch, they won't be used
anymore even if present).

As mingw.org already treats winsup/mingw and winsup/w32api as separate
repos[1], that should do the trick for us without forcing them to move.
Given our long-standing cooperation until now, I think it's the least we
could do.


[1] http://mingw.org/wiki/Official_CVS_Repository

More information about the Cygwin-patches mailing list