From: "Robb, Sam" <sam.robb@timesys.com>
To: <bigone@qon.lao.net>, <cygwin-licensing@cygwin.com>
Subject: RE: Mass Distribution Without Source, Bittorrent
Date: Tue, 31 Jan 2006 15:15:00 -0000 [thread overview]
Message-ID: <3D848382FB72E249812901444C6BDB1D0908A15B@exchange.timesys.com> (raw)
> I read about the GPL: the shop should provide the source code
> with the binary.
>
> I plan to distribute Cygwin free of charge to several
> thousands local schools, universities, user groups,
> research/scientific institute, magazine etc.
>
> There are 5 ISO CD (600 Mb): 2 binary and 3 source code.
A complete snapshot of a cygwin mirror includes a bunch of
stuff you probably don't want to distribute. Each package
generally has at least two source and binary packages - the
current version, plus the previous version.
If you are only interested in distributing the current version
of each package, you can reduce the distribution size by
eliminating the previous binary/source archive for each package.
This is what my company (TimeSys) does when we distribute cygwin
snapshots to our customers. At least for the moment, we're
able to squeeze everything onto one binary CD and one source CD.
If you were already planning on shipping two binary CDs, then
this may allow you avoid potential GPL issues while still only
shipping two CDs.
-Samrobb
next reply other threads:[~2006-01-31 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 15:15 Robb, Sam [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-31 14:11 big one
2006-01-31 14:34 ` Corinna Vinschen
2006-01-31 15:15 ` Reini Urban
2006-01-31 17:09 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D848382FB72E249812901444C6BDB1D0908A15B@exchange.timesys.com \
--to=sam.robb@timesys.com \
--cc=bigone@qon.lao.net \
--cc=cygwin-licensing@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).