From: Randall R Schulz <rrschulz@cris.com>
To: Charles Wilson <cwilson@ece.gatech.edu>
Cc: Markus Hoenicka <Markus.Hoenicka@uth.tmc.edu>, cygwin@cygwin.com
Subject: Re: "local install"?
Date: Fri, 01 Mar 2002 08:00:00 -0000 [thread overview]
Message-ID: <5.1.0.14.2.20020301075448.00aaf730@pop3.cris.com> (raw)
In-Reply-To: <3C7FA2A1.1090208@ece.gatech.edu>
Chuck,
I cannot get setup.exe to permit multiple selection of mirrors, so how is
this magical seamless multi-mirror integration achieved? Can it be done
without running setup.exe more than once? If not, what's the advantage over
separate download and install?
Furthermore, why doesn't the multi-mirror technique, however effected, work
for separated download and install, too?
Lastly, am I correct in believing that if one wants to download anything
but not install it (source, e.g., or packages used by some at one's site
but not by all) that separate download and install is the only way to
accomplish this?
It still seems to me that control freaks are going to do as I do: Separate
download and install.
Randall Schulz
Mountain View, CA USA
At 07:47 2002-03-01, Charles Wilson wrote:
>Randall R Schulz wrote:
>
>
>>I don't understand this. You get maximum flexibility by separate
>>"Download from Internet" and "Install from Local Directory" operations.
>>That way you can download sources and have them at hand without
>>unconditionally installing them.
>>
>>By copying my local installation cache to a CD, I can save others very
>>large downloads. I cannot see this as a loss of functionality.
>>
>>Can you tell me some functionality only available when one uses "Install
>>from Internet?"
>
>
>Sure: merging multiple "mirrors" into a seamless single-view
>installation. (Or, merging an official mirror site + "Bob's archive of
>cool cygwin packages" + "My company's local cygwin ports" into a single,
>always-up-to-date single seamless installation). Sure, you could manually
>download the packages you are interested in from all 27 sites, merge them
>into a single local repo, and then do 'install-from-local' -- but setup's
>"extra functionality" automatically handles that stuff for you -- just
>point-n-click.
>
>--Chuck
--
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:[~2002-03-01 16:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 2:13 Toni Mueller
2002-03-01 7:13 ` Brian Keener
2002-03-01 7:24 ` Markus Hoenicka
2002-03-01 7:33 ` Randall R Schulz
2002-03-01 7:44 ` Markus Hoenicka
2002-03-01 7:49 ` Charles Wilson
2002-03-01 8:00 ` Randall R Schulz [this message]
2002-03-01 10:55 ` Charles Wilson
[not found] ` <5.1.0.14.2.20020301160226.02538020@pop3.cris.com>
2002-03-01 16:31 ` Charles Wilson
2002-03-01 16:34 ` Randall R Schulz
2002-03-01 16:40 ` Charles Wilson
2002-03-01 16:57 ` Randall R Schulz
2002-03-01 17:05 ` Robert Collins
2002-03-01 17:37 ` Randall R Schulz
2002-03-01 17:23 ` Robert Collins
2002-03-01 7:47 Mark Sheppard
2002-03-01 8:08 ` Markus Hoenicka
2002-03-01 16:02 Robert Collins
2002-03-01 16:02 Robert Collins
2002-03-01 16:04 Robert Collins
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=5.1.0.14.2.20020301075448.00aaf730@pop3.cris.com \
--to=rrschulz@cris.com \
--cc=Markus.Hoenicka@uth.tmc.edu \
--cc=cwilson@ece.gatech.edu \
--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).