This is the mail archive of the
mailing list for the Cygwin project.
Re: mingw path/mount handling code (Was: Re: Practical method for automatic Cygwin install?)
- From: Brian Dessent <brian at dessent dot net>
- To: cygwin at cygwin dot com
- Date: Fri, 09 Dec 2005 08:29:06 -0800
- Subject: Re: mingw path/mount handling code (Was: Re: Practical method for automatic Cygwin install?)
- References: <20051123035342.9E89913C1A1@cgf.cx> <20051123192106.GA757@trixie.casa.cgf.cx> <Pine.GSO.email@example.com> <4384DF7D.142487C5@dessent.net> <20051123213551.GA2952@trixie.casa.cgf.cx> <4399A748.CA4107C7@dessent.net> <20051209160320.GA10690@trixie.casa.cgf.cx>
- Reply-to: cygwin at cygwin dot com
Christopher Faylor wrote:
> I think there is very small chance of that. IIRC, some of that code is
> straight out of the cygwin DLL itself.
> I think that anyone who had studied the cygwin path handling code would
> have a tough time proving that there was no "taintedness" if they tried
> to produce a library under a different license.
Crud. Well I suppose from a code reuse standpoint it would still make
sense to factor out that stuff so that setup and cygcheck (and anything
else GPL) can share it. But without a relicensed version it still means
that 3PPs that want to gracefully distribute Cygwin stuff have to write
all the mount table stuff themselves (or run /bin/mount, which I guess
is the mantra anyway.)
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html