public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@redhat.com>
To: Cygwin-L <cygwin@cygwin.com>
Subject: Re: time to download
Date: Sat, 10 Feb 2001 10:29:00 -0000	[thread overview]
Message-ID: <20010210132922.A4523@redhat.com> (raw)
In-Reply-To: <4.3.1.2.20010210124955.00b8f490@pop.ma.ultranet.com>

On Sat, Feb 10, 2001 at 12:58:09PM -0500, Larry Hall (RFK Partners, Inc) wrote:
>It certainly would be beneficial to have some way of determining
>dependencies so that a smaller set could be downloaded by those who want
>just that.

Possibly RPM would be one way to solve this but that would be a major
change for setup.exe.

Of course, even with RPM, you still have to figure out the dependencies.
I recently installed an RPM for "bind" from rawhide.redhat.com.  The
dependency wasn't set to include one of the newer, other, bind packages,
so I spent a while trying to figure out why my domain name server wasn't
working anymore.

Anyway, I really would like someone to modify setup.exe to allow either:

1) Categorization of download packages (development, user, etc.) <easy>.

2) Interpackage dependency.  <hard>

3) Batch-mode operation. <???>

Hopefully, it is obvious to everyone that improving setup.exe is very
low on the list of Red Hat priorities for Cygwin.  I did manage to swing
a certain amount of time for DJ to work on this prior to his leaving the
group but this was a one-time thing.

We've had a lot of high-quality submissions from the net for setup.exe.
I hope that someone will be willing to take on the challenge of adding
the next level of functionality to the package.

Btw, I should mention that the licensing restrictions for setup.exe are
not exactly the same as for the Cygwin DLL and other utilities.  So far,
I have not imported setup.exe into our internal tree and have kept the
program as a strictly net offering.  That means that I don't have to ask
people to sign a release.  I just need an email assurance that there
employer disclaims all ownership to whatever they are working on and
allows them to put the code into setup.exe with no strings attached.

cgf

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2001-02-10 10:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-09 13:20 murthy ramana
2001-02-09 13:34 ` Larry Hall (RFK Partners, Inc)
2001-02-09 14:05 ` Warren Young
2001-02-09 14:24   ` Larry Hall (RFK Partners, Inc)
2001-02-10  1:06     ` Warren Young
2001-02-10 10:02       ` Larry Hall (RFK Partners, Inc)
2001-02-10 10:29         ` Christopher Faylor [this message]
2001-02-09 20:20 ` Tim Prince
2001-02-09 14:03 Barry Buchbinder
2001-02-09 14:09 ` Christopher Faylor
2001-02-11 23:22 Jean Jordaan
2001-02-11 23:37 ` Erdely, Michael
2001-02-11 23:44   ` Erdely, Michael
2001-02-12  8:05     ` Christopher Faylor

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=20010210132922.A4523@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).