Mailing-List:	contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe:	<mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-apps/>
List-Post:	<mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To:	mailing list cygwin-apps AT sources DOT redhat DOT com
content-class:	urn:content-classes:message
MIME-Version:	1.0
Subject:	RE: whats left before releasing setup?
X-MimeOLE:	Produced By Microsoft Exchange V6.0.4417.0
Date:	Wed, 7 Nov 2001 11:25:32 +1100
Message-ID:	<EA18B9FA0FE4194AA2B4CDB91F73C0EF08F27C@itdomain002.itdomain.net.au>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic:	whats left before releasing setup?
Thread-Index:	AcFnHb2zDai/fFcvQQ+VS0Kofy8iNQABBFBg
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	<bkeener AT thesoftwaresource DOT com>, "CA List" <Cygwin-Apps AT Cygwin DOT Com>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id fA70I9p25589

> -----Original Message-----
> From: Brian Keener [mailto:bkeener AT thesoftwaresource DOT com]
> 
> 
> Robert Collins wrote:
> > > version of cygwin then store the last cache wherever 
> setup is located - just as 
> > > setup has always done in the past with the setup.log and 
> setup.log.full. 
> > 
> > Thats an ok idea. However, you will also need to change the 
> logic for
> 
> Well what does setup do now with setup.log and setup.log.full 
> or have those been 
> removed

Those files are one off - they have no impact on the user. Last-cache,
last-mirror, do have an impact on the user on the next run of setup.exe.
So the treatment of the two sets of files is orthogonal IMO.

> > Because there are two basic download only scenarios.
> > 1) Download to take to other machines via zip disk etc - 
> this machine
> > doesn't get involved in cygwin at all. 
> > 2) Download for _this machine_ and for other via a 
> networked cache dir.
> > You may not want to install the packages you download immediately on
> > this machine.
> 
> Actually both of these scenarios are exactly what I am 
> talking about and in either 
> case Cygwin might or might not be installed and I may or may 
> not be ready to say 
> where I want my cygwin root to be and I might want to back up 
> my cache of setup and 
> its downloaded packages and it sure would be nice if I only 
> had one location to deal 
> with. 

Having only one location is the point. Where does setup.exe live? Do you
update *that* setup.exe when you update the cache? What if you are
testing a setup.exe and dont' want to overwrite the current one? What
about just clicking on setup.exe on the web and going Run... (as
covvered before).
 
> As I parting thought on this subject let me simply say 
> Last-cache is a setup file 
> not a cygwin file just as setup.log and setup.log.full are 
> setup files and therefore 
> belong with setup.  

I disagree. If that is the case, why do *all* the files in/etc/setup
exist. They are all "setup" files by that logic.

Setup is a cygwin program, integrated with cygwin, and designed to
install cygwin. The files it uses are *files* not registry settings to
aid that integration. Lastly as covered before setup.log and .log.full
are very different to last-cache.
 
> I understand you have made your decision and obviously as 
> maintainer that is your 

I don't seem to be disagreeing with you and Earnie (and anyone else who
holds this opinion). I'll be very happy to see the root selection box go
away again for download only mode.

> right and you will accept a patch so I will now bow out - 
> others may carry on this 
> discussion if they so choose.

Rob

- Raw text -