From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10781 invoked by alias); 22 Apr 2008 06:59:55 -0000 Received: (qmail 10757 invoked by uid 22791); 22 Apr 2008 06:59:54 -0000 X-Spam-Check-By: sourceware.org Received: from mail.elsag-solutions.com (HELO esmail.elsag.de) (62.154.225.82) by sourceware.org (qpsmtpd/0.31) with SMTP; Tue, 22 Apr 2008 06:59:36 +0000 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [HEADSUP] Let's start a Cygwin 1.7 release area Date: Tue, 22 Apr 2008 06:59:00 -0000 Message-ID: References: <20080415090849.GZ23852@calimero.vinschen.de> <20080415141730.GA21313@ednor.casa.cgf.cx> <20080415154400.GL23852@calimero.vinschen.de> <20080415175923.GA21976@ednor.casa.cgf.cx> <20080415183856.GM23852@calimero.vinschen.de> <4804FB2D.6040802@byu.net> <4805645E.63ED0505@dessent.net> <20080416084447.GN23852@calimero.vinschen.de> <20080421140428.GA7301@calimero.vinschen.de> <20080421174811.GZ23852@calimero.vinschen.de> <20080421201510.GE23852@calimero.vinschen.de> <480D7F83.300AE579@dessent.net> From: =?iso-8859-1?Q?J=F6rg_Schaible?= To: X-IsSubscribed: yes 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/msg00267.txt.bz2 cygwin-apps-owner@cygwin.com wrote: > Corinna Vinschen wrote: >=20 >> it just occured to me that I need the exact key name which setup will >> use to store the root directory of the installation. I nedd it to >> get cygcheck working, even if it's not installed into the same path >> as the Cygwin DLL.=20 >>=20 >> "{HKLM,HKCU}\Software\Cygwin\???" >>=20 >> ??? =3D "Setup\root" maybe? Or with a version number? >=20 > A good question. I haven't implemented anything yet, so we can choose > whatever we want. I wonder if it's really necessary to have a whole > subkey for this since at the moment there is only the one value that > setup will read. How about simply "\Software\Cygwin\rootdir"? >=20 > That reminds me of something... I've always been a bit annoyed that > people always resort to manually editing the registry to > remove Cygwin, > when umount is the documented and preferred method. But now, we will > have no such utility to suggest and so to remove Cygwin the > user will be > forced to use regedit. regtool remove {HKLM,HKCU}\Software\Cygwin\??? > Combined with the fact that most > users trip over > the fact that sometimes ACLs on files like /var/log/sshd.log require > them to take ownership before deleting, I would like to be > able to offer > an uninstaller. This would handle checking for running > Cygwin processes > and prompting to exit them (or terminating them), stopping and > uninstalling all Cygwin services, deleting the entire Cygwin tree, > removing start menu and desktop icons, removing everything from the > registry, and whatever else is necessary. It would be the nuclear > option, deleting without remorse all traces with one click; I think > users want this. It would of course be a standalone MinGW app like > setup.exe, except that it would get installed somewhere in > the tree, and > added to the add/remove applet. Anyway, SHTDI and everything > but I just > want to float the idea to gauge response. Guess, it's nevertheless a good idea ... - J=F6rg