From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1204 invoked by alias); 12 Apr 2008 15:15:38 -0000 Received: (qmail 1183 invoked by uid 22791); 12 Apr 2008 15:15:35 -0000 X-Spam-Check-By: sourceware.org Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Sat, 12 Apr 2008 15:15:18 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 5C4846D4312; Sat, 12 Apr 2008 17:15:15 +0200 (CEST) Date: Sat, 12 Apr 2008 15:15:00 -0000 From: Corinna Vinschen To: cygwin-apps@cygwin.com Subject: Re: [HEADSUP] Let's start a Cygwin 1.7 release area Message-ID: <20080412151515.GG23852@calimero.vinschen.de> Reply-To: cygwin-apps@cygwin.com Mail-Followup-To: cygwin-apps@cygwin.com References: <47FCB20D.DACDC9FA@dessent.net> <20080409121559.GA15549@calimero.vinschen.de> <47FCC01A.A9ABB7B9@dessent.net> <20080409143139.GA5920@ednor.casa.cgf.cx> <20080409162803.GL23852@calimero.vinschen.de> <20080411151333.GO23852@calimero.vinschen.de> <480014A9.62EF4E0F@dessent.net> <20080412113540.GD23852@calimero.vinschen.de> <20080412122232.GE23852@calimero.vinschen.de> <4800AF02.DC1B3AF5@dessent.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4800AF02.DC1B3AF5@dessent.net> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com X-SW-Source: 2008-04/txt/msg00167.txt.bz2 On Apr 12 05:45, Brian Dessent wrote: > Corinna Vinschen wrote: > > > When I start setup-1.7, it seems to find the already existing c:/cygwin > > installation. Even though I choose "C:/cygwin-2" as installation path, > > the new setup-2.ini content is compared against the already existing > > installation. The result is that setup-1.7 offers to install only > > the single changed package: cygwin itself. > > Right, it reads /etc/setup/installed.db (where /etc is derived from the > mount table) to see what the current versions are. > > > Why is setup using the information from the existing installation > > even if I choose to install into another directory? Is it because > > the mount points in the registry are looked at? That's not correct > > anymore, given that the registry mount points are not used for the > > new installation anyway. > > > > Is it possible to change setup so that it ignores the registry mount > > points? And it must nort write new ones either, btw... > > Oh. Teaching it not to read or write to the mount table in the registry > is going to be a lot more work than just telling it to read a different > .ini file. I'll see what I can do, but until then I think we'll just > have to tell people to do the switching manually (mount -m/umount -A). Thank you. I also found, when setup doesn't have the mount points it doesn't seem to be able to take the /etc/setup/installed.db from the path entered as root directory. It installs happily all base packages again a second time. Probably we will still need *some* registry entry. Setup could create one for its own purpose, just to find the installation path. Maybe the registry value should use a version number, so that we can have two parallel installation again, should we ever release a -3 distro... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat