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

That didn't come out right.  I was not addressing this particularly at
Chris.  The last few messages just seemed to have a bit of an undertone to
them...

I have gotten a few ideas which I'll now consider on how to apply.

-----Original Message-----
From: Masterson, Dave 
Sent: Thursday, January 25, 2001 12:38 PM
To: 'cygwin@cygwin.com'
Subject: RE: Questions about Cygwin's setup...


Hmmm.  Was I being offensive in what I said?  If so, I didn't mean to be.  I
only thought I was asking some questions about setup and expanding on my
reasoning for those questions.  My hope was simply that maybe someone would
say "oh, you could do that this way."  Failing that, I'd go look at how I
want to install Cygwin more and see what I could hack up.

-----Original Message-----
From: Christopher Faylor [ mailto:cgf@redhat.com ]
Sent: Thursday, January 25, 2001 12:16 PM
To: cygwin@cygwin.com
Subject: Re: Questions about Cygwin's setup...


On Thu, Jan 25, 2001 at 12:04:30PM -0800, Masterson, Dave wrote:
>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...?

As DJ has indicated, it is not easy to have an executable update itself in
Windows.

Earnie's method will work.  Since setup.exe requires human intervention
to run, you really don't have a choice as far as automating anything is
concerned.

Unless you are willing to make the modifications to setup.exe yourself,
speculating on what "would be nice" is not going to get your problem
solved.

cgf

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

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

             reply	other threads:[~2001-01-25 12:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-25 12:35 Masterson, Dave [this message]
  -- 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:29 Masterson, Dave
2001-01-25 11:56 Masterson, Dave
2001-01-25 12:16 ` Christopher Faylor
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=5C838890A2EDD411AFB2009027CC67091A2B7B@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).