From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Max Bowsher" <maxb@ukf.net>, <cygwin@cygwin.com>
Subject: RE: Why do we need a mirroring tool - setup.exe based or not?
Date: Tue, 30 Apr 2002 04:06:00 -0000 [thread overview]
Message-ID: <FC169E059D1A0442A04C40F86D9BA7600C5F57@itdomain003.itdomain.net.au> (raw)
> -----Original Message-----
> From: Max Bowsher [mailto:maxb@ukf.net]
> Sent: Tuesday, April 30, 2002 7:13 PM
> i.e. they will not want [prev] packages once the superceding
> [curr] package has proved itself.
And how do you test that?
> Perhaps I'm missing something obvious, but surely setup.exe
> is all we need?
What if you want a local repository with consolidated dirs for
distribution of cygwin within a corporate LAN?
What if you want to download all packages matching (.*Xfree.*)?
What if you want all curr and prev packages kept cached, but older than
that deleted automatically?
I'm sure there are more examples.
Download only mode is a primitive form of mirroring. If we had a good
mirror tool, we could -consider- removing download only mode completely.
The problem is that setup is aimed at *installing* cygwin. The
maintenance functionality has grown ontop of that base. I'm refactoring
as fast as I have time to, but the guts of setup still reflect that
origin. Everything we do that makes setup more 'complete' makes it
bigger. This isn't good.
Finally, I'd like to see a much smaller setup that has nearly no
options, and kickstarts the process by downloading cygwin1.dll, a
setup.exe that can call out to libraries, and any core support files for
that. Then from there you can install anything you want. The point being
that the absolute minimum is quite small, and is non-optional.
Rob
--
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 reply other threads:[~2002-04-30 9:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-30 4:06 Robert Collins [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-30 3:42 Max Bowsher
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=FC169E059D1A0442A04C40F86D9BA7600C5F57@itdomain003.itdomain.net.au \
--to=robert.collins@itdomain.com.au \
--cc=cygwin@cygwin.com \
--cc=maxb@ukf.net \
/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).