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
Subject: Re: whats left before releasing setup?
From: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>
To: bkeener AT thesoftwaresource DOT com
Cc: CA List <Cygwin-Apps AT Cygwin DOT Com>
In-Reply-To: <VA.000009aa.0047c414@thesoftwaresource.com>
References: <1005048150 DOT 1442 DOT 0 DOT camel AT lifelesswks>
	<3BE7D865 DOT 8F33E90A AT yahoo DOT com> <1005050815 DOT 1471 DOT 12 DOT camel AT lifelesswks> 
	<VA DOT 000009aa DOT 0047c414 AT thesoftwaresource DOT com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Evolution/0.15 (Preview Release)
Date: 07 Nov 2001 09:42:03 +1100
Message-Id: <1005086524.2726.49.camel@lifelesswks>
Mime-Version: 1.0
X-OriginalArrivalTime: 06 Nov 2001 22:48:16.0025 (UTC) FILETIME=[1F4DC890:01C16715]

On Wed, 2001-11-07 at 02:48, Brian Keener wrote:
> Robert Collins wrote:
> > I'll happily accept a patch to not write the last-cache file for
> > download only installs. That combined with an alteration to cygpath I've
> > prepared to return NULL on failure should allow the cache read routine
> > to fail safely too. (with a check for NULL of course :]).
> >
> 
> I don't think we are saying to not write the last-cache file as I for one like 
> setup to be able to remember where the cache of downloaded packages 

so do I. 

> is and I 
> believe it has done that for a while - even before categories and dependencies. 

No, I wrote that code 3 days ago. Until then it always reset the cache
location to the current working directory.

> What we are saying is don't expect the user to start the install when no cygwin 
> is installed by forcing the entry of the cygwin root so that you can store the 
> last-cache file in the cygwin directory.  In the absence of an installed 

Yes. Thats what I am saying I will accept a patch for.

> 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
reading the last cache file to try /etc/setup/last-cache and if that
fails or cygpath returns NULL (which is what my patch in the last
related mail is for) fallback to trying last-cache in the CWD.
 
> At the point of doing a Download only why am I even concerned with the mount 
> points except to determine if cygwin is installed or not (which by the way is a 
> good reason but should a download only even care) and then to base certain 
> other functions on that result. 

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. 

IMO these are both valid, and as you can see one machine is in not
currently installed and the other is.

Rob