From: Brian Dessent <brian@dessent.net>
To: cygwin-licensing@cygwin.com
Subject: Re: 1NIWGYC.DLL ??
Date: Fri, 16 Dec 2005 02:57:00 -0000 [thread overview]
Message-ID: <43A227EC.DBB68282@dessent.net> (raw)
In-Reply-To: <005301c601cb$8cc46d70$2602a8c0@itefixb>
Tevfik Karagülle wrote:
> on the target machine. However, It is tempting to find an ultimate solution to this problem:
> renaming dlls and registry references. I have tested and verified that it is technically possible.
Just renaming the DLL and registry keys is not enough to avoid conflicts
with an existing cygwin1.dll. You will also have to modifiy the name of
the shared memory region and all other shared objects.
From a licensing point of view you can do anything you want as long as
you provide the source packages to build the binaries. AFAIK. IANAL.
etc.
Brian
next prev parent reply other threads:[~2005-12-16 2:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-16 2:19 Tevfik Karagülle
2005-12-16 2:57 ` Brian Dessent [this message]
2005-12-16 3:20 ` Christopher Faylor
2005-12-16 20:50 Tevfik Karagülle
2005-12-18 17:10 ` Reini Urban
2005-12-18 19:01 ` Christopher Faylor
2005-12-19 12:20 Tevfik Karagülle
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=43A227EC.DBB68282@dessent.net \
--to=brian@dessent.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).