This is the mail archive of the
mailing list for the Cygwin project.
Re: Concurrent versions of cygwin1.dll on one system
- From: Christopher Faylor <cgf at redhat dot com>
- To: cygwin-apps at cygwin dot com
- Date: Tue, 9 Jul 2002 13:06:44 -0400
- Subject: Re: Concurrent versions of cygwin1.dll on one system
- References: <20020708173949.L97906-100000@localhost> <20020708233457.GB24240@redhat.com> <3D2A28AE.firstname.lastname@example.org> <3D2A9AE2.email@example.com>
- Reply-to: cygwin-apps at cygwin dot com
And, here, ladies and gentlemen, is the somewhat rarer form of the
cygwin/cygwin-apps confusion where a thread, started in cygwin@cygwin,
is moved to cygwin-apps rather than the other way around.
Are we having fun yet?
On Tue, Jul 09, 2002 at 10:12:18AM +0200, Lapo Luchini wrote:
>>And roll your own "IvoWin". (Remember, tho, cygwin is GPL; therefore
>>IvoWin will be GPL and you must make the source code available to
>>whomever you give the binary. Ditto for your app - but that's already
>>true for your app, since it currently links to cygwin itself)
>The app can in fact comply with any OSI-approved open source license I
>think, as of "note" on page http://cygwin.com/licensing.html
>Another easy method to distribute a program which uses cygwin is to
>create an http or ftp directory with packages and setup.ini with binary
>and sources for your project and simply let users install a "real" (even
>if minimal) cygwin.
>This is IMHO the best way to go.
>Lapo 'Raist' Luchini
>firstname.lastname@example.org (PGP & X.509 keys available)
>http://www.lapo.it (ICQ UIN: 529796)