Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<067801c1021e$679e8140$806410ac@local>
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	"Michael A. Chase" <mchase AT ix DOT netcom DOT com>, <cygwin AT sources DOT redhat DOT com>
References:	<00b701c1010a$39ddea30$6464648a AT ca DOT boeing DOT com> <20010629223139 DOT B11334 AT redhat DOT com> <008a01c1013a$470a8fd0$6464648a AT ca DOT boeing DOT com> <005e01c101e3$439f1e70$6464648a AT ca DOT boeing DOT com>
Subject:	Re: Local Setup Cache
Date:	Sun, 1 Jul 2001 21:10:12 +1000
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4522.1200
X-OriginalArrivalTime:	01 Jul 2001 10:57:47.0717 (UTC) FILETIME=[A9FA2F50:01C1021C]

----- Original Message -----
From: "Michael A. Chase" <mchase AT ix DOT netcom DOT com>
To: <cygwin AT sources DOT redhat DOT com>
Sent: Sunday, July 01, 2001 2:04 PM
Subject: Local Setup Cache


> Currently, setup.exe downloads package files from whatever mirror site a
> user selects and then installs the packages.  As new versions are
produced,
> they get downloaded and installed to replace the old version, but the
> archive files for the old version are not removed.  Eventually this may
fill
> significant amounts of disk space with obsolete files.
>
> I see two likely ways for handling this problem:
>
> 1.  Provide a program that removes files from the cache if they are not
> listed in setup.ini.  The problem with this is that inexperienced users
are
> unlikely to run the cleanup program often enough for it to do any good.
>
> 2.  Modify setup.exe so it will remove obsolete files.  The problem with
> this is that it adds yet another feature to setup.exe.

Setup.exe is used to bootstrap and maintain the _system_. IMO adding
non-installation features to setup.exe just increases it's size with little
benefit... but dselect uses a similar technique, however they just remove
_all_ cached files on the basis that once a files been installed it's not
needed again (unlesss you are installing another machine, when you would say
"N"). The question is only asked when no errors are encountered.

>  Does anyone see any other possibilities?

Not really - in setup vs out of setup is pretty binary :}. I'm against it
(even given my dselect comparison above) while setup.exe is used to install
local files by scanning. If setup could be called like "setup --install
my-local-file-path" in addition to the cache directory, then yes. Otherwise
I think its too hard to make sure we don't wipe out some users local files
that were never downloaded by setup.exe in the first place. If we do do
something in-setup the dselect model akes a lot of sense to me. (delete it
all, the setup is complete after all).

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/

- Raw text -