public inbox for cygwin-licensing@cygwin.com
 help / color / mirror / Atom feed
From: "David Benn" <dbenn@computer.org>
To: <cygwin-licensing@cygwin.com>
Subject: Including just cygwin1.dll in an archive
Date: Sun, 11 Sep 2005 21:49:00 -0000	[thread overview]
Message-ID: <000501c5b6c8$7eda0920$0400a8c0@nova> (raw)

Hi all

From the cygwin Licensing terms on the web, it appears to me that I
cannot distribute an archive that looks like this:

Archive:  scope_dist.zip
  Length     Date   Time    Name
 --------    ----   ----    ----
        0  09-10-05 23:43   scope_dist/
   971080  09-10-05 23:43   scope_dist/cygwin1.dll
        0  09-10-05 23:43   scope_dist/driver/
   121158  09-10-05 23:43   scope_dist/driver/ascom.dll
    22297  09-10-05 23:43   scope_dist/driver/skeleton.dll
    22706  09-10-05 23:43   scope_dist/scope_client.dll
    22814  09-10-05 23:43   scope_dist/tests.exe
 --------                   -------
  1160055                   7 files

for end users, irrespective of whether another archive containing full
sources, Makefiles etc is separately released. 

The point of contention here is the inclusion of cygwin1.dll. This is an
*unmodified* cygwin1.dll.

Can someone please advise me or tell me where to find out?

I'd be happy to replace the need for this dll with static linking,
assuming that's even *possible* under cygwin. If it is, a pointer would
be appreciated. 

Of course, I'd have thought that whether the code is in the cygwin1.dll
or in my binaries is a fine distinction.

Note that this is a freeware project so paying money for license fees is
not my first preference.

Thanks in advance for any advice.

Rgds,

DJB
 


             reply	other threads:[~2005-09-11 21:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-11 21:49 David Benn [this message]
2005-09-11 22:24 ` Christopher Faylor
2005-09-12 12:13   ` David Benn

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='000501c5b6c8$7eda0920$0400a8c0@nova' \
    --to=dbenn@computer.org \
    --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).