Compliance with the GPL (cygwin)

Compliance with the GPL (cygwin)

[Charles Wilson]

License compliance for programs which use cygwin.
   VCDImager (cygiwin-1.3.6)
   cdrdao    (cygwin-1.1.8)
   VCDEasy-full (BOTH cygwin's, since it includes the above)

I'm ignoring the issue of multiple cygwin versions installed on the same 
system, which may conflict with a "real" cygwin environment on the 
user's computer, and with each other....that's a different topic (and I 
don't know what the "right" solution is, so...skip it)

Here, I'm only concerned with projects that are not complying with the 
GPL license of the cygwin DLL.  Since all of these projects are part of 
the open-source milieu, I know that any infraction of the license of 
another open-source project is unintentional...but violations should be 
remedied.

Note that it's very easy for each of these projects to comply with 
cygwin's license (the GPL): just
   1) make their own source available (true already, for most of them)
   2) put a tarball of the (appropriate) cygwin DLL source code on
      their ftp site with their other downloads,
   3) ditto for other cygwin-linked libraries (zlib, libxml, libjpeg)
      if applicable
   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?)
   5) A plug for the cygwin project itself (http://www.cygwin.com)
      would be nice, but definitely not necessary for license compliance.

To dampen the inevitable arguments about the GPL:
If you distribute a binary (such as cygwin1.dll) that is under the GPL, 
then YOU have to also distribute the source code for THAT binary.  You 
cannot just say "get the source over there, at cygwin.com".  If you 
don't believe me, READ the GPL.  READ the commentary on it by RMS. In 
addition, if you link your executable to a GPL'ed shared library (lik 
cygwin1.dll), then you must distribute the source code for your 
executable, as well, or you lose the right to use cygwin1.dll.  It's all 
there in the GPL.

Chuck
cygwin hacker

VCDEasy includes:

  cdrdao-1.1.5
    which contains cygwin1.dll-1.1.8
    cdrdao doesn't distribute the source of cygwin,
      although it is opensource itself.  They DO
      distribute a cygwin-linked "windows" binary
      along with a copy of cygwin1.dll itself
      (but no mention of the cygwin project anywhere)
    BTW: not even cygwin distributes or uses this old
      version anymore.  Fortunately, the VCDImager guys
      went thru the effort of extracting from CVS and
      creating a cygwin-1.1.8 tarball, back when they
      were using that old version.  The cdrdao guys could
      a) get it from them & redistribute it, or b) update
      to a newer cygwin and get the source from us.

  mjpeg-tools
    which contains cygwin1.dll-1.3.6 and cygjpeg6b.dll
    Now, the mjpegtools project doesn't seem to provide
      windows binaries; the windows (e.g. cygwin) port
      seems to be something the VCDEasy folks did.

  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.

So, to sum up:

   VCDImager project: seems mostly compliant; need a reminder to
   include also OTHER source code (zlib, libxml)

   cdrdao: open source, but not complying with the cygwin GPL.
     they need to distribute the source for:
       cygwin-1.1.8

   mjpeg-tools: they don't distribute cygwin-linked binaries, so
     they are under no obligation to distribute cygwin sources.

   VCDEasy (includes all of the above): provides no source, whatsoever,
     for cygwin, cygwin-linked binaries, cygwin-linked dlls, nothing.
     NADA.  ZILCH.  Totally non-compliant.
   VCDEasy needs to distribute the source for:
        cygwin-1.1.8
        cygwin-1.3.6
        zlib
        libxml
        jpeg
        mjpeg-tools
        vcdimager
        cdrdao
      AND
        itself.

Contact info:

VCDImager:    hvr@hvrlab.org
cdrdao:       Manuel Clos  at  cdrdao-devel@lists.sourceforge.net
mjpeg-tools:  (not needed)
VCDEasy:      delphi.stuff@vcdhelp.com


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Compliance with the GPL (cygwin)

[delphi.stuff]

VCDEasy is originally a Graphical Interface helping users to use VCDImager. 
Then I added cdrdao and some mjpeg tools to ease the VCD creation process. 
If I include in some VCDEasy distributions these command line tools, it is 
only to easy the end user setup. Note that VCDEasy is a Win32 native 
application, made with the free Personal Borland Delphi 6, it does not use 
cygwin directly.

I bought some components so I do not have the rights to publish them. So 
now, based on the fact that I will not publish the source, what should I do 
? Stop my VCDEasy freeware development ? Or does advertise for cygwin 
directly on my application can be enough ? Something else ? Distribute the 
Win32 gui only and tell the user to download everything else themselves... 
in this case I think I am ok with all the licenses... but it won't help the 
end users...  I am not deliberately violating the cygwin GPL license, I 
only try to help end users, I hope you can understand that. As I said, 
VCDEasy is a Win32 native application, it does not use cygwin directly.

Note that the situation is worse as I identified at least two commercial 
packages that sell my application (including VCDImager and CDRDAO) without 
any rights... They are making money...

delphi.stuff

At 19:46 12/04/2002 -0400, Charles Wilson wrote:
>License compliance for programs which use cygwin.
>   VCDImager (cygiwin-1.3.6)
>   cdrdao    (cygwin-1.1.8)
>   VCDEasy-full (BOTH cygwin's, since it includes the above)
>
>I'm ignoring the issue of multiple cygwin versions installed on the same 
>system, which may conflict with a "real" cygwin environment on the user's 
>computer, and with each other....that's a different topic (and I don't 
>know what the "right" solution is, so...skip it)
>
>Here, I'm only concerned with projects that are not complying with the GPL 
>license of the cygwin DLL.  Since all of these projects are part of the 
>open-source milieu, I know that any infraction of the license of another 
>open-source project is unintentional...but violations should be remedied.
>
>Note that it's very easy for each of these projects to comply with 
>cygwin's license (the GPL): just
>   1) make their own source available (true already, for most of them)
>   2) put a tarball of the (appropriate) cygwin DLL source code on
>      their ftp site with their other downloads,
>   3) ditto for other cygwin-linked libraries (zlib, libxml, libjpeg)
>      if applicable
>   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?)
>   5) A plug for the cygwin project itself (http://www.cygwin.com)
>      would be nice, but definitely not necessary for license compliance.
>
>To dampen the inevitable arguments about the GPL:
>If you distribute a binary (such as cygwin1.dll) that is under the GPL, 
>then YOU have to also distribute the source code for THAT binary.  You 
>cannot just say "get the source over there, at cygwin.com".  If you don't 
>believe me, READ the GPL.  READ the commentary on it by RMS. In addition, 
>if you link your executable to a GPL'ed shared library (lik cygwin1.dll), 
>then you must distribute the source code for your executable, as well, or 
>you lose the right to use cygwin1.dll.  It's all there in the GPL.
>
>Chuck
>cygwin hacker
>
>VCDEasy includes:
>
>  cdrdao-1.1.5
>    which contains cygwin1.dll-1.1.8
>    cdrdao doesn't distribute the source of cygwin,
>      although it is opensource itself.  They DO
>      distribute a cygwin-linked "windows" binary
>      along with a copy of cygwin1.dll itself
>      (but no mention of the cygwin project anywhere)
>    BTW: not even cygwin distributes or uses this old
>      version anymore.  Fortunately, the VCDImager guys
>      went thru the effort of extracting from CVS and
>      creating a cygwin-1.1.8 tarball, back when they
>      were using that old version.  The cdrdao guys could
>      a) get it from them & redistribute it, or b) update
>      to a newer cygwin and get the source from us.
>
>  mjpeg-tools
>    which contains cygwin1.dll-1.3.6 and cygjpeg6b.dll
>    Now, the mjpegtools project doesn't seem to provide
>      windows binaries; the windows (e.g. cygwin) port
>      seems to be something the VCDEasy folks did.
>
>  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.
>
>So, to sum up:
>
>   VCDImager project: seems mostly compliant; need a reminder to
>   include also OTHER source code (zlib, libxml)
>
>   cdrdao: open source, but not complying with the cygwin GPL.
>     they need to distribute the source for:
>       cygwin-1.1.8
>
>   mjpeg-tools: they don't distribute cygwin-linked binaries, so
>     they are under no obligation to distribute cygwin sources.
>
>   VCDEasy (includes all of the above): provides no source, whatsoever,
>     for cygwin, cygwin-linked binaries, cygwin-linked dlls, nothing.
>     NADA.  ZILCH.  Totally non-compliant.
>   VCDEasy needs to distribute the source for:
>        cygwin-1.1.8
>        cygwin-1.3.6
>        zlib
>        libxml
>        jpeg
>        mjpeg-tools
>        vcdimager
>        cdrdao
>      AND
>        itself.
>
>Contact info:
>
>VCDImager:    hvr@hvrlab.org
>cdrdao:       Manuel Clos  at  cdrdao-devel@lists.sourceforge.net
>mjpeg-tools:  (not needed)
>VCDEasy:      delphi.stuff@vcdhelp.com



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Compliance with the GPL (cygwin)

[Herbert Valerio Riedel]

[-- Attachment #1: Type: text/plain, Size: 2307 bytes --]

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 
> 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
 
> 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.
> 
> So, to sum up:
> 
>    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,
-- 
Herbert Valerio Riedel       /    Phone: (EUROPE) +43-1-58801-18840
Email: hvr@hvrlab.org       /    Finger hvr@gnu.org for GnuPG Public Key
GnuPG Key Fingerprint: 7BB9 2D6C D485 CE64 4748  5F65 4981 E064 883F
4142

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]

Re: Compliance with the GPL (cygwin)

[Herbert Valerio Riedel]

[-- Attachment #1: Type: text/plain, Size: 1681 bytes --]

On Sat, 2002-04-13 at 10:58, delphi.stuff wrote:
> I bought some components so I do not have the rights to publish them. So 
> now, based on the fact that I will not publish the source, what should I do 
> ?
you have no obligation at all to publish your source to vcdeasy, since
you don't link to any GPL'ed code.

> Stop my VCDEasy freeware development ? Or does advertise for cygwin 
> directly on my application can be enough ? Something else ? Distribute the 
> Win32 gui only and tell the user to download everything else themselves... 
well, either provide the source code yourself;

or maybe easier for you, but a bit more work for your users:

distribute the self contained win32 gui alone in a zip file
and point the users to the cdrdao and vcdimager binary packages
directly;

maybe you can do this by some installer? this would also make it harder
for people to sell your application, if this really annoys you..
this installer would download the required zip files by http/ftp and
unzip them in the correct destination, maybe moving around a bit the
files....

just an idea...

> Note that the situation is worse as I identified at least two commercial 
> packages that sell my application (including VCDImager and CDRDAO) without 
> any rights... They are making money...
do you mind give more information about them? I'd like to check whether
they include source code (offers) for GPL'ed code... ;-)

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

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]

Re: Compliance with the GPL (cygwin)

[Charles Wilson]

delphi.stuff wrote:

> 
> VCDEasy is originally a Graphical Interface helping users to use 
> VCDImager. Then I added cdrdao and some mjpeg tools to ease the VCD 
> creation process. If I include in some VCDEasy distributions these 
> command line tools, it is only to easy the end user setup. Note that 
> VCDEasy is a Win32 native application, made with the free Personal 
> Borland Delphi 6, it does not use cygwin directly.


Fair enough.  If VCDeasy.exe only CALLS the cygwin-linked programs, and 
doesn't actually link to cygwin or another GPLed project/library itself, 
then you're safe -- as far as the source code to VCDEasy *itself* is 
concerned.

 
> I bought some components so I do not have the rights to publish them. So 
> now, based on the fact that I will not publish the source, what should I 
> do ? Stop my VCDEasy freeware development ? Or does advertise for cygwin 
> directly on my application can be enough ? Something else ? Distribute 
> the Win32 gui only and tell the user to download everything else 
> themselves... in this case I think I am ok with all the licenses... but 
> it won't help the end users...  I am not deliberately violating the 
> cygwin GPL license, I only try to help end users, I hope you can 
> understand that. As I said, VCDEasy is a Win32 native application, it 
> does not use cygwin directly.


Of course you not violating the license purposely.  A lot of folks don't 
really understand their obligations under the GPL -- which serve to 
protect and propagate the software freedoms that the GPL grants.  I'm 
just trying to help -- and I'll prove it below.


> Note that the situation is worse as I identified at least two commercial 
> packages that sell my application (including VCDImager and CDRDAO) 
> without any rights... They are making money...


There's nothing wrong with selling GPLed programs that you (or these 
commercial packages) don't own.  (That's how Red Hat Linux and Mandrake 
and SuSe and ... make their money).  So no worries there.  All you (and 
the commercial folks that are distributing VCDEasy) need to do is ensure 
that your users (customers) can obtain the source from you.  (e.g. it's 
no good saying "go get the source from those guys, over there).

So, it seems that all *you* (delphi.stuff) need to do is grab the 
following source codes and put them up on your website somewhere, and 
say "Some libraries and programs invoked by VCDEasy are GPLed, although 
VCDEasy is not itself GPL (and isn't tainted by the GPL since it only 
*executes* these subprograms; it is not linked to them).  You can get 
the source code for those GPLed components here <link to your /src 
directory on your webserver/ftpserver>".

        cygwin-1.1.8
        cygwin-1.3.6
        zlib
        libxml
        jpeg
        mjpeg-tools
        vcdimager
        cdrdao

To help you out, here are some direct links so that you can download the 
src tarballs (all are available here for the next week or so, but they 
will be going away so make sure to physically put them on your own site)

http://www.neuro.gatech.edu/users/cwilson/vcd-src/

Hope that helps.

--Chuck

**************************************************

For VCDImager:

   cygwin-1.3.6-6-src.tar.bz2
taken from the VCDImager website...

   zlib-1.1.3-6-src.tar.gz
an md5 analysis show that 1.1.3-6 is the version of cygz.dll you are using

   libxml2-2.4.12-1-src.tar.bz2
stay tuned.  VCDImager doesn't use version 2.4.13-1 nor 2.4.17-1, which 
are the only versions currently available on the cgywin download site. 
I'm checking with Robert Collins, the cygwin maintainer of that package, 
to see if he has kept 2.4.12-1-src and can send it to me.

   vcdimager-0.7.12.tar.gz
   VCDImager itself: you seem to be using version 0.7.12

********************************************************

For mjpeg-tools

   cygwin-1.3.6-6-src.tar.bz2
taken from the VCDImager website...(same as above)

   jpeg-6b-4-src.tar.gz
an md5 analysis show that 6b-4 is the version of cygjpeg6b.dll you are using

    mjpegtools-1.4.1.tar.gz
    mjpegtools-1.6.0-beta1.tar.gz
    mjpegtools-1.6.0-beta2.tar.gz
mjpegtools itself.  I couldn't determine which version you were using, 
so I grabbed all of the currently distributed src tarballs

**************************************************

For CdrDao

   cygwin-1.1.8-2-src.tar.bz2

   cdrdao-1.1.5.src.tar.gz

**************************************************


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Compliance with the GPL (cygwin)

[Charles Wilson]

Herbert Valerio Riedel wrote:

>>Note that it's very easy for each of these projects to comply with 
>>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
>>


Yep, I saw that VCDImager was already GPL compliant, with the exception 
of the zlib and libxml libraries.  But, this all snowballed when I was 
taking a look at VCDEasy -- which led to VCDImager, cdrdao, mjpegtools, 
etc...


> will follow as soon as I get time to


Understood.  I've done some analysis on the dlls (to determine exact 
versions) and put the source here, to make your job easier

http://www.neuro.gatech.edu/users/cwilson/vcd-src/

I don't have the src for the specific version of libxml2 that you are 
using; if you got the DLL from the cygwin dist, it must be v 2.4.12-1 
(which is no longer available from the cygwin site) since the signature 
of your cygxml2-2.dll doesn't match either of cygwin's current xml dlls: 
2.4.13-1 and 2.4.17-1.

I'm trying to track down the official cygwin libxml2 packages for v 
2.4.12 from the cygwin libxml maintainer (Robert Collins), and if the 
signatures there match your DLL, then I'll put that source up too.

If they don't match, then I guess you built libxml yourself; you'll have 
to handle the src issue (and delphi.stuff will need to get those sources 
from you, once you've posted them, since he is redistributing your 
windows (cygwin) port).

In any case, if you use the -src packages I collected at the above site, 
you'll need to copy them and put them on your site; mine will go away in 
about a week.


> 
>>   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


Again, I knew that vcdimager did this; the others didn't AFAICT.


>>   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


As above -- but no big deal, this isn't necessary.


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


? Do you link the libs statically?  If so, you still need to supply src 
for the libs, since they are linked against cygwin1.dll they inherit the 
GPLness as well as your own code (although I think libxml is already 
gpl, as is vcdimager.  zlib has its own license, but cygwin's GPL still 
applies to the zlib source...)


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


No probs.


> 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.


Well, what Robert said, plus: I'm the cgywin maintainer for zlib and 
jpeg (which VCDEasy includes in its dist of mjpegtools).  And, as a 
major contributor to the cygwin project, I feel a certain responsibility 
when I see cygwin1.dll as well.

I'm glad (nay, overjoyed) to see people using cygwin and cygwin-ports; I 
just want folks to use them legally. :-)

--Chuck


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Compliance with the GPL (cygwin)

[Charles Wilson]

> For VCDImager:
>   libxml2-2.4.12-1-src.tar.bz2
> stay tuned.  VCDImager doesn't use version 2.4.13-1 nor 2.4.17-1, which 
> are the only versions currently available on the cgywin download site. 
> I'm checking with Robert Collins, the cygwin maintainer of that package, 
> to see if he has kept 2.4.12-1-src and can send it to me.

Okay, 2.4.12-1 is not available (Robert doesn't have it any more). 
However, that may be a moot point anyway: I think Herbert built 
cygxml2-2.dll himself from "regular" sources.

In any case, the various libxml libraries are drop in replacements, so 
simply replacing cygxml2-2.dll with the version from here:

ftp://mirrors.rcn.net/mirrors/sources.redhat.com/cygwin/contrib/libxml2/
   libxml2-2.4.17-1-src.tar.bz2
   libxml2-2.4.17-1.tar.bz2 <<< unpack and extract the dll >>>

should be sufficient.

--Chuck


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Compliance with the GPL (cygwin)

[Charles Wilson]

The source code I put here: 
http://www.neuro.gatech.edu/users/cwilson/vcd-src/

to help you guys get compliant with the GPL is going away in 48 hours. 
I can't keep that much stuff up there indefinitely...

--Chuck

Charles Wilson wrote:

> 
>        cygwin-1.1.8
>        cygwin-1.3.6
>        zlib
>        libxml
>        jpeg
>        mjpeg-tools
>        vcdimager
>        cdrdao
> 
> To help you out, here are some direct links so that you can download the 
> src tarballs (all are available here for the next week or so, but they 
> will be going away so make sure to physically put them on your own site)
> 
> http://www.neuro.gatech.edu/users/cwilson/vcd-src/
> 
> Hope that helps.
> 
> --Chuck
> 
> **************************************************
> 
> For VCDImager:
> 
>   cygwin-1.3.6-6-src.tar.bz2
> taken from the VCDImager website...
> 
>   zlib-1.1.3-6-src.tar.gz
> an md5 analysis show that 1.1.3-6 is the version of cygz.dll you are using
> 
>   libxml2-2.4.12-1-src.tar.bz2
> stay tuned.  VCDImager doesn't use version 2.4.13-1 nor 2.4.17-1, which 
> are the only versions currently available on the cgywin download site. 
> I'm checking with Robert Collins, the cygwin maintainer of that package, 
> to see if he has kept 2.4.12-1-src and can send it to me.
> 
>   vcdimager-0.7.12.tar.gz
>   VCDImager itself: you seem to be using version 0.7.12
> 
> ********************************************************
> 
> For mjpeg-tools
> 
>   cygwin-1.3.6-6-src.tar.bz2
> taken from the VCDImager website...(same as above)
> 
>   jpeg-6b-4-src.tar.gz
> an md5 analysis show that 6b-4 is the version of cygjpeg6b.dll you are 
> using
> 
>    mjpegtools-1.4.1.tar.gz
>    mjpegtools-1.6.0-beta1.tar.gz
>    mjpegtools-1.6.0-beta2.tar.gz
> mjpegtools itself.  I couldn't determine which version you were using, 
> so I grabbed all of the currently distributed src tarballs
> 
> **************************************************
> 
> For CdrDao
> 
>   cygwin-1.1.8-2-src.tar.bz2
> 
>   cdrdao-1.1.5.src.tar.gz
> 
> **************************************************
> 



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: Compliance with the GPL (cygwin)

[Robert Collins]

> -----Original Message-----
> From: Herbert Valerio Riedel [mailto:hvr@hvrlab.org] 
> Sent: Saturday, April 13, 2002 7:17 PM

> >    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?)

Just a note (for Chuck). I'm pretty sure that it is a corollary of the
GPL that the source be advertised -  along with the specific licence
being offered. 

> >    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

I wonder if you are aware that cygwin has libxml2 in the distribution
now - you can link to the .dll for your unstable series as well, should
you desire.
 
> 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.

I can't speak for Chuck, but I think he's got a similar feeling to me.
My interest in seeing the GPL followed is threefold.
1) If the GPL loses the 'threat' power it has now, it will take a test
case to reinstate that. 
2) In my opinion it's the Right Thing to do - to make the source
directly available instead of hoping that someone else has it available.
3) While the GPL is not perfect it's the licence I choose to do the bulk
of my development under, and I've contributed quite a few hours of
'free' work to Cygwin - I don't like to see that abused without credit
being given. 

I really appreciate your quick and friendly response to Chucks email
though - good one!

Cheers,
Rob

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/