From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-licensing@cygwin.com
Subject: Re: Licensing/Installer Questions
Date: Wed, 01 Mar 2006 14:19:00 -0000 [thread overview]
Message-ID: <20060301141544.GS3184@calimero.vinschen.de> (raw)
In-Reply-To: <9149702.1141221528157.JavaMail.chartpacs@mac.com>
On Mar 1 08:58, Michael Banks wrote:
> Hello Corinna,
>
> Thank you for the prompt reply. I'm still a little confused.
>
> 1) Licensing. Could you please explain what "linking against Cygwin" means? I'm guessing that is for trying to port a Unix application to Windows? We're just wanting to use a few of the open-source tools (grep, find, ghostscript, etc.), so I'm guessing we do *not* need to purchase a special license, but we just want to be sure.
Linking in the compiler/linker/runtime-loader sense. Linking against
Cygwin means building an application which relies on functions provided
by the Cygwin library. Roughly, if you application works even if Cygwin
is not present, you're off the hook. If your application refuses to
start without Cygwin, you're not.
> 2) Installer. We could use some specifics on how to comply with the cygwin lincensing.
The installer has nothing to do with licensing. All tools, which
are open-sourced should be accompanied with their respective sources.
The exact style (zip file, tar archive, CD installer, ...) has nothing
to do with the licensing, except that a user should get the sources
the same way as they get the binaries.
As for your specific installer packaging questions, they don't belong to
cygwin-licensing. Please ask this sort of question on the normal cygwin
mailing list <cygwin AT cygwin DOT com>.
> On Wednesday, March 01, 2006, at 05:02AM, Corinna Vinschen <XXXXXXX-XXXXXX@XXXXXX.XXX> wrote:
> [...]
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
next prev parent reply other threads:[~2006-03-01 14:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 9:17 Michael Banks
2006-03-01 10:02 ` Corinna Vinschen
2006-03-01 14:05 ` Michael Banks
2006-03-01 14:19 ` Corinna Vinschen [this message]
2006-03-03 12:17 ` Michael Banks
2006-03-03 13:01 ` Corinna Vinschen
2006-03-03 15:51 ` Dave Korn
2006-03-03 15:32 ` Dave Korn
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=20060301141544.GS3184@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).