public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Joshua Daniel Franklin <joshuadfranklin@yahoo.com>
To: jmaynard@conmicro.cx, cygwin@cygwin.com
Subject: Re: Packaging software built with cygwin
Date: Thu, 06 Feb 2003 13:24:00 -0000	[thread overview]
Message-ID: <20030206132434.30278.qmail@web20009.mail.yahoo.com> (raw)

> > 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.

> 4.6 MB times how many versions will I need to keep around? Before I removed
> them from the Hercules site, I had four sets of the Cygwin DLLs,
> corresponding to four versions of Hercules they were needed for. Every time
> I release a new version of Hercules, that's another source tarball I'd need.

I realize this is pretty late in the discussion, but I have a suggestion that
might work. Online, you could distribute only the latest, known-working version
of Hercules with cygwin1.dll and the source to that version of cygwin1.dll--no,

you don't need the source to gcc (that's used to build it) nor the source to
TeX (that's used for the documentation) nor the source to Linux (that's also
GPL'd), why would you? 

For older versions, you could put a note stating that due to online space
requirements older cygwin versions are not available online. If you don't have
offline space issues, you could keep an archive around on your personal machine
(or on CD or tape or punch-card or wherever) for emergencies. 
Hopefully in the future some good bug reports can be used to track down
whatever is causing the backward-compaitibility to break, so this would no
longer be necessary. 

Hope this helps and have a nice day.

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

--
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/

             reply	other threads:[~2003-02-06 13:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-06 13:24 Joshua Daniel Franklin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-05 20:44 Franz Wolfhagen
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
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

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=20030206132434.30278.qmail@web20009.mail.yahoo.com \
    --to=joshuadfranklin@yahoo.com \
    --cc=cygwin@cygwin.com \
    --cc=jmaynard@conmicro.cx \
    /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).