[PATCH] setup -e, --separate-src-dirs option

Christian Franke Christian.Franke@t-online.de
Thu Dec 15 19:02:00 GMT 2011

Christopher Faylor wrote:
> On Thu, Dec 15, 2011 at 07:38:14AM +0100, Christian Franke wrote:
>> It is actually difficult to guess the origin of some source files. For
>> example:
>> /usr/src/0.19-data-auto-imports.patch (from flexdll-0.26-1)
>> /usr/src/blacklist.txt (from ca-cerficates-*)
>> /usr/src/config-rpath.patch (from some gcc-* ?)
> That's not difficult.  It's trivial to figure out where these files
> came from.

Even if this is the case (it IMO isn't), there is at least one other 
drawback. Due to missing version numbers in some names, it is impossible 
to keep several versions of the same package in /usr/src.

> I still don't understand the need for this.

Please note that I suggested to *keep* the old behavior and let the 
*user* opt-in for the new one. I actually missed that feature since I 
started to use Cygwin many years ago.

>    If everyone thinks it's
> a good idea than why don't we eschew code bloat and make package
> developers use this technique.  Otherwise, unless you inspect the
> source files, you'll be adding a separate layer of directory to
> /usr/src for packages that don't need it.

Another more complex approach would be: Examine the 
PACKAGE-VERSION-src.tar.bz file first. If all top level names start with 
(or contain?) PACKAGE-VERSION, install in /usr/src, else install in 
/usr/src/PACKAGE-VERSION. But I will not provide such a patch this year :-)


More information about the Cygwin-apps mailing list