X-Spam-Check-By: sourceware.org Date: Fri, 30 Jun 2006 16:49:44 -0400 (EDT) From: Igor Peshansky Reply-To: cygwin AT cygwin DOT com To: Dave cc: cygwin AT cygwin DOT com, f g Subject: Re: uninstall cygwin In-Reply-To: <44A554B2.1060508@gmail.com> Message-ID: References: <20060630092232 DOT 50874 DOT qmail AT web27410 DOT mail DOT ukl DOT yahoo DOT com> <44A554B2 DOT 1060508 AT gmail DOT com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Fri, 30 Jun 2006, Dave wrote: > Igor Peshansky wrote: > > On Fri, 30 Jun 2006, f g wrote: > > > > > I would like to uninstall a Cygwin installation under > > > Windows XP: to do this I follow the instruction in > > > > You'll also want to delete the registry key, as outlined in the above > > instructions. Oh, and deleting the directory won't remove any > > shortcuts created by the Cygwin installation packages (like those in > > the Start Menu or on the desktop, or the associations created by the > > "chere" package), so it's better to use setup.exe to uninstall > > everything first, *then* delete the directory and the registry key. > > Just to clarify, Igor's procedure won't remove the chere associations > that he mentioned. > > If you don't recognise "chere", then you don't have any associations to > remove. If someone else set things up for you, run the following command > (before uninstalling cygwin) to identify any associations: > > chere -l > > To remove the associations, run > > chere -u -s > > for each shell, where is the shell you installed > (cmd/ash/bash/tcsh/pdksh/zsh). That's from memory (and I don't uninstall > that often:), see man chere for accurate information. Right, thanks for the clarification, Dave. I forgot that chere needed to be explicitly invoked to add the association (and thus explicitly invoked to remove it as well). This also applies to other packages that need to be explicitly configured (e.g., sshd, cron, etc). In any case, the advice still applies -- any package that was installed using Cygwin setup will need to be uninstalled using Cygwin setup to give the preremove scripts a chance to run. Technically, the preremove scripts should undo whatever the postinstall scripts did (if they don't, it's a packaging bug). Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte." "But no -- you are no fool; you call yourself a fool, there's proof enough in that!" -- Rostand, "Cyrano de Bergerac" -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/