Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Subject: Re: Compliance with the GPL (cygwin)
From: Herbert Valerio Riedel <hvr AT hvrlab DOT org>
To: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
Cc: cygwin AT cygwin DOT com, cdrdao-devel AT lists DOT sourceforge DOT net,
   delphi DOT stuff AT vcdhelp DOT com
In-Reply-To: <3CB771E9.20006@ece.gatech.edu>
References: <3CB771E9 DOT 20006 AT ece DOT gatech DOT edu>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature";
	boundary="=-LsAFKAAAaqRj/nwROx2k"
Date: 13 Apr 2002 11:17:00 +0200
Message-Id: <1018689420.23745.152.camel@janus.txd.hvrlab.org>
Mime-Version: 1.0

--=-LsAFKAAAaqRj/nwROx2k
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Sat, 2002-04-13 at 01:46, Charles Wilson wrote:
> License compliance for programs which use cygwin.
>    VCDImager (cygiwin-1.3.6)

[..]

> Note that it's very easy for each of these projects to comply with=20
> cygwin's license (the GPL): just
>    1) make their own source available (true already, for most of them)
ftp://ftp.vcdimager.org/pub/vcdimager/

>    2) put a tarball of the (appropriate) cygwin DLL source code on
>       their ftp site with their other downloads,
ftp://ftp.vcdimager.org/pub/cygwin/

>    3) ditto for other cygwin-linked libraries (zlib, libxml, libjpeg)
>       if applicable
will follow as soon as I get time to

>    4) mention the availability of the source code for libraries
>       used to create their windows port somewhere on their
>       webpage (not strictly necessary, but what's the point of
>       1 -- 3 if you don't advertise it?)
http://www.vcdimager.org/software.phtml

>    5) A plug for the cygwin project itself (http://www.cygwin.com)
>       would be nice, but definitely not necessary for license compliance.
http://www.vcdimager.org/software.phtml
=20
> To dampen the inevitable arguments about the GPL:

[..]
>   VCDImager
>     which contains cygwin1.dll-1.3.6, cygz.dll, and cygxml-2.dll
>     VCDImager provides the src for cygwin, but not
>       zlib or xml.  (Actually, they provide LOTS of different
>       src tarballs -- probably more than they need to -- but
>       all for various versions of cygwin, not zlib/xml.
>=20
> So, to sum up:
>=20
>    VCDImager project: seems mostly compliant; need a reminder to
>    include also OTHER source code (zlib, libxml)
[..]

will do so;

btw, I do this just for the unstable series; as soon as the official
stable series come out, they'll lack the .dll's

btw2: libxml2 was provided in source, I just happen to have deleted it
by accident

ps: just wondering, which personal interest do you have, that others
(we) comply to the terms? -- plz don't see this question as personal
attack or something alike.

regards,
--=20
Herbert Valerio Riedel       /    Phone: (EUROPE) +43-1-58801-18840
Email: hvr AT hvrlab DOT org       /    Finger hvr AT gnu DOT org for GnuPG Public Key
GnuPG Key Fingerprint: 7BB9 2D6C D485 CE64 4748  5F65 4981 E064 883F
4142

--=-LsAFKAAAaqRj/nwROx2k
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQA8t/eMSYHgZIg/QUIRAp/+AJ9JEx4aWEaJSnoQC+Yhjim/K2CKewCgjCFe
SpQd48tHtBAWIpD9R+butXo=
=YT8R
-----END PGP SIGNATURE-----

--=-LsAFKAAAaqRj/nwROx2k--