From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: Re: Packaging software built with cygwin
Date: Wed, 05 Feb 2003 17:54:00 -0000 [thread overview]
Message-ID: <20030205175543.GB17331@redhat.com> (raw)
In-Reply-To: <20030205111822.B9661@thebrain.conmicro.cx>
On Wed, Feb 05, 2003 at 11:18:22AM -0600, Jay Maynard wrote:
>On Tue, Feb 04, 2003 at 10:32:46PM -0500, Christopher Faylor wrote:
>> On Tue, Feb 04, 2003 at 08:48:03PM -0600, Jay Maynard wrote:
>> >On Tue, Feb 04, 2003 at 09:31:43PM -0500, Igor Pechtchanski wrote:
>> >>Remember that linking against some version of libcygwin.a doesn't mean
>> >>you have to keep to the corresponding version of cygwin1.dll. Since
>> >>it's loaded dynamically, all you need is for the functions you need to
>> >>be present in the new DLL. This is generally the case.
>> >Present *and* working the same or compatibly. Unfortunately, we've
>> >found that that's not the case.
>> I sincerely doubt that you've found a problem where something that was
>> available in an older DLL is not available in a newer one. The only
>> case I can think of where this happened is the dropping of //a for
>> /cygdrive/a.
>
>There are numerous bug reports in the Hercules mailing list archives from
>folks who have tried to run Hercules with a different version of
>cygwin1.dll than the one Hercules was built against. In every case,
>installing the version that Hercules was built against corrected the
>problem.
>
>It may be intended to be upward compatible, but that's not our experience.
Ok. I'm not going to start scouring random other mailing lists for
cygwin bug reports so I suppose this situation will continue In absence
of any details, it's fruitless to carry this discussion any further.
>>However, just in case you need to hear it, it is true that you have to
>>provide the sources for the cygwin DLL if you want to distribute it.
>
>I have stopped distributing the Cygwin DLL entirely, since meeting this
>requirement would impose larger requirements for disk space and/or time
>than I can afford. (See how the GPL has improved sharing of programs!
>Pfaugh.)
Hmm. Looks like you just couldn't resist, huh?
>Of the five DLLs that Hercules needs (cygwin1.dll, cygintl-2.dll,
>cygiconv-2.dll, cygbz2-1.dll, and cygz.dll), only one is GPLed. This
>imposes requirements on distribution of the complete package that do
>not apply to the other platforms that Hercules is distributed for.
>This is hardly going to make porting packages from Linux to Windows
>easier.
The source tarball for cygwin is 4.6M. I don't understand why this
is a huge hardship but, frankly, I don't really care.
>I've considered, and rejected, the idea of distributing my own
>setup.ini file. The problem is that it seems to be as much of a moving
>target as Cygwin itself.
A setup.ini with just the cygwin DLL in it seems pretty simple.
Btw, perhaps it is not your intention, but I catch a whiff of innuendo
here makes me wonder if you're really asking for help or just here to
make some statements.
>I would suggest that, if it is desired to promote the development of
>applications on the Cygwin platform, serious consideration be made to
>making it as simple as possible to install only those portions of
>Cygwin that the application requires. This means just the necessary
>DLLs, without all of the interactive use baggage. Right now, that's
>nearly impossible.
Supporting other people's distributions is not a core focus of
setup.exe. However, if this is important to you it should be pretty
easy for you to submit patches to do what you want.
cgf
--
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/
next prev parent reply other threads:[~2003-02-05 17:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-04 22:34 Packaging software built with Cygwin Jay Maynard
2003-02-04 23:27 ` Igor Pechtchanski
2003-02-05 1:46 ` Jay Maynard
2003-02-05 2:31 ` Igor Pechtchanski
2003-02-05 2:48 ` Jay Maynard
2003-02-05 3:32 ` Packaging software built with cygwin Christopher Faylor
2003-02-05 13:38 ` Nigel Stewart & Fiona Smith
2003-02-05 14:11 ` Christopher Faylor
2003-02-05 14:14 ` Jay Maynard
2003-02-05 17:18 ` Jay Maynard
2003-02-05 17:30 ` Nigel Stewart & Fiona Smith
2003-02-05 17:52 ` Max Bowsher
2003-02-06 13:17 ` Nigel Stewart & Fiona Smith
2003-02-06 13:43 ` Max Bowsher
2003-02-06 14:05 ` Nigel Stewart & Fiona Smith
2003-02-05 18:19 ` Christopher Faylor
2003-02-05 17:54 ` Christopher Faylor [this message]
2003-02-05 18:55 ` Jay Maynard
2003-02-05 20:43 ` Christopher Faylor
2003-02-05 21:41 ` Robert Collins
2003-02-06 9:59 ` Ronald Landheer-Cieslak
2003-02-06 13:24 ` Jay Maynard
2003-02-05 20:44 Franz Wolfhagen
2003-02-06 13:24 Joshua Daniel Franklin
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=20030205175543.GB17331@redhat.com \
--to=cgf@redhat.com \
--cc=cygwin@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).