public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Masterson, Dave" <dmasters@rational.com>
To: 'Earnie Boyd' <cygwin@cygwin.com>
Subject: RE: Questions about Cygwin's setup...
Date: Thu, 25 Jan 2001 11:56:00 -0000	[thread overview]
Message-ID: <5C838890A2EDD411AFB2009027CC67091A2B79@cupex3.rational.com> (raw)

Oh.  Yeah, I could do that, but it seems to be a bit of overkill.  I mean I
think the steps you are suggesting are:

* Wget automatically mirrors *.tar.gz files from sources.redhat.com (or
mirror).

* I occassionally use Setup.exe to unpackage the new *.tar.gz's and update
my central area.

It would seem that it would be just as easy to use Setup for both steps...?

-----Original Message-----
From: Earnie Boyd [ mailto:earnie_boyd@yahoo.com ]
Sent: Thursday, January 25, 2001 10:46 AM
To: Masterson, Dave
Cc: 'Earnie Boyd'
Subject: Re: Questions about Cygwin's setup...


"Masterson, Dave" wrote:
> 
> Hmmm.  Wget is not a complete answer.  What if my "user" doesn't want to
> mirror it on his system because he feels the network access to the server
is
> fast enough?  Also, there is still the issue of the registry entries
> (remember, I'm not "installing" it on the user's system).
> 

I was suggesting the the "Cygwin Administrator" use wget to mirror
Cygwin for the "Central Repository" to get the most up to date
versions.  The "Cygwin Administrator" would then update the "Central
Repository".  I wasn't suggesting that every user mirror Cygwin, that
wouldn't be necessary.

Earnie.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

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

             reply	other threads:[~2001-01-25 11:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-25 11:56 Masterson, Dave [this message]
2001-01-25 12:16 ` Christopher Faylor
  -- strict thread matches above, loose matches on Subject: below --
2001-01-26  6:36 Robinow, David
2001-01-25 14:18 Dan Lipofsky
2001-01-25 12:35 Masterson, Dave
2001-01-25 12:29 Masterson, Dave
2001-01-25 11:45 Masterson, Dave
2001-01-25 12:14 ` Christopher Faylor
2001-01-25 12:19 ` Larry Hall (RFK Partners, Inc)
2001-01-25 10:28 Masterson, Dave
2001-01-25 10:36 ` Christopher Faylor
2001-01-25 10:46 ` Earnie Boyd
2001-01-24 18:27 Masterson, Dave
2001-01-24 18:39 ` DJ Delorie
2001-01-24 19:20 ` Earnie Boyd
2001-01-24 20:22 ` Christopher Abbey
2001-01-24 17:21 Masterson, Dave
2001-01-24 17:52 ` Earnie Boyd
2001-01-24 18:17   ` DJ Delorie
2001-01-25 15:04     ` Paul Garceau
2001-01-24 18:00 ` DJ Delorie

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=5C838890A2EDD411AFB2009027CC67091A2B79@cupex3.rational.com \
    --to=dmasters@rational.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).