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
From: "Andre Oliveira da Costa" <costa AT cade DOT com DOT br>
To: "DJ Delorie" <dj AT delorie DOT com>
Cc: <cygwin AT sources DOT redhat DOT com>
Subject: RE: setup.exe aborting at the end of an update
Date: Mon, 30 Oct 2000 17:36:21 -0200
Message-ID: <000c01c042a8$aea239a0$e100000a@costa>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
In-Reply-To: <200010301844.NAA27429@envy.delorie.com>

> Well, you could download a snapshot (not recommended) or pull the
> sources for cygwin from an install (but you might not get the latest).
>
> CVS is certainly the recommended way, and using "cvs diff" provides
> patches that are very easy for us to apply.

To be honest, RCS has always been enough for me, and for that reason I've
been delaying getting into CVS. I guess the time has come to evolve.
However, for this particular problem, I might take a snapshot, hoping that I
will get to some results earlier.

> If you're running the latest setup, one of the dialogs asks for the
> local directory to use.  It's there.

You mean the "select install root directory" prompt? It points to c:\cygwin,
and Windows' "find" command reports there are no .ini files under this tree.

> It might be on your desktop if you ran setup right off the web page.

I checked, it's not there either. Where is this little devil hiding? =T

> No, the tarballs aren't there.  Those are listings of installed files
> (*.gz).  Tarballs are *.tar.gz.

S*t! Sorry for this stupid overlook. It only took me a find for *.tar.gz to
see where the latest tarballs were copied to. Running setup.exe from this
directory and choosing "Install from current dir" bombs *exactly* the same
way -- including the hex numbers reported.

> No, setup is supposed to "just work".  We address FAQs by changing
> setup, not by obscure documentation.

Ok. Guess I will have to keep troubling you, then...

Best,

Andre Costa


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com