From: "Max Bowsher" <maxb@ukf.net>
To: <cygwin@cygwin.com>
Subject: Re: setup 2.194.2.24: Bug (?) in downloading from internet
Date: Mon, 29 Apr 2002 04:07:00 -0000 [thread overview]
Message-ID: <00a901c1ef61$35f85d60$42a18c09@wdg.uk.ibm.com> (raw)
In-Reply-To: <FC169E059D1A0442A04C40F86D9BA7600C5F42@itdomain003.itdomain.net.au>
Robert Collins <robert.collins@itdomain.com.au> wrote:
>> -----Original Message-----
>> From: Sam Edge [mailto:sam_edgeZZZ@hotmail.com]
>> Sent: Sunday, April 28, 2002 8:17 PM
>> Every version of setup.exe I've used exhibits this annoying
>> behaviour but them I'm new here.
>>
>> I agree with Daniele. I install different subsets of the
>> packages on several machines. I also like to keep a copy of
>> the most up-to-date versions of packages that I don't
>> currently use on any of them, in case I need them where I've
>> no (or poor) access to the 'Net.
>
> So use a mirroring tool! Setup.exe is -not- designed for this. If you
> want a setup.ini parsing mirroring tool, take me up on my offer to help
> someone leverage the setup.ini codebase to build a mirroring tool.
>
> Rob
But setup.exe has operated in the correct way in the past! Why write a new tool,
when fixing a bug in the current one would do all that needs to be done? NB: I'm
not saying 'go fix that now'. When (if? ;-) I find time to understand the setup
code, I will do this, if no one has beaten me to it.
Max.
--
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-04-29 9:35 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-28 4:47 Robert Collins
2002-04-28 8:08 ` Sam Edge
2002-04-28 15:04 ` Gary R. Van Sickle
2002-04-28 15:09 ` Sam Edge
2002-04-28 15:30 ` Charles Wilson
2002-04-28 16:05 ` Christopher Faylor
2002-04-28 16:09 ` Sam Edge
2002-04-28 19:08 ` Michael A Chase
2002-04-29 0:06 ` Christopher Faylor
2002-04-29 0:57 ` Cliff Hones
2002-04-29 4:58 ` Robert Collins
2002-04-28 16:05 ` Sam Edge
2002-04-29 13:01 ` Using a real mirroring tool Charles Wilson
2002-04-29 17:17 ` Charles Wilson
2002-04-29 17:21 ` Charles Wilson
2002-04-29 17:46 ` Charles Wilson
2002-04-30 6:20 ` Sam Edge
2002-04-30 10:09 ` Volker Quetschke
2002-04-30 13:43 ` Volker Quetschke
2002-04-30 14:00 ` Michael A Chase
2002-04-29 4:07 ` Max Bowsher [this message]
2002-04-29 4:24 ` setup 2.194.2.24: Bug (?) in downloading from internet Robert Collins
-- strict thread matches above, loose matches on Subject: below --
2002-04-29 2:35 Robert Collins
2002-04-29 2:26 Robert Collins
2002-04-29 5:42 ` Sam Edge
2002-04-29 5:49 ` Robert Collins
2002-04-29 7:46 ` Sam Edge
2002-04-30 1:58 ` Gary R. Van Sickle
2002-04-29 8:27 ` Christopher Faylor
2002-04-28 22:34 Alec Mihailovs
2002-04-28 23:51 ` Charles Wilson
2002-04-28 10:15 Robert Collins
2002-04-28 8:14 Robert Collins
2002-04-28 9:56 ` Kurt Roeckx
2002-04-28 3:17 Daniele Mezzetti
2002-04-28 4:31 ` Sam Edge
2002-04-26 8:34 Robert Collins
2002-04-26 7:10 Robert Collins
2002-04-26 7:57 ` Alexei Lioubimov
2002-04-25 8:55 Alexei Lioubimov
2002-04-25 11:00 ` Larry Hall (RFK Partners, Inc)
2002-04-26 7:03 ` Alexei Lioubimov
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='00a901c1ef61$35f85d60$42a18c09@wdg.uk.ibm.com' \
--to=maxb@ukf.net \
--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).