Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Message-ID: <010c01c1097e$1a417030$6464648a@ca.boeing.com>
From: "Michael A. Chase" <mchase AT ix DOT netcom DOT com>
To: "Jan Nieuwenhuizen" <janneke AT gnu DOT org>
Cc: <cygwin-developers AT cygwin DOT com>
References: <m3wv5i75bc DOT fsf AT appel DOT lilypond DOT org><20010709105557 DOT A19708 AT redhat DOT com><00dc01c10895$0f8e2e10$6464648a AT ca DOT boeing DOT com> <m3vgl1ta7n DOT fsf AT appel DOT lilypond DOT org>
Subject: Re: Install and Uninstall Scripts
Date: Tue, 10 Jul 2001 13:09:12 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400

The main problem I see with the way you had /etc/postremove/... is that if
the script is part of the package, it will be removed by setup.exe before it
has a chance to get executed.  A pre-uninstall script could be executed and
renamed to *.done before setup.exe starts deleting files.

A pre-uninstall script can always copy something to /etc/postinstall to get
the effect of a postremove script.

--
Mac :})
** I normally forward private questions to the appropriate mail list. **
Give a hobbit a fish and he eats fish for a day.
Give a hobbit a ring and he eats fish for an age.
----- Original Message -----
From: "Jan Nieuwenhuizen" <janneke AT gnu DOT org>
To: "Michael A. Chase" <mchase AT ix DOT netcom DOT com>
Cc: <cygwin-developers AT cygwin DOT com>; <cygwin AT cygwin DOT com>
Sent: Tuesday, July 10, 2001 02:17
Subject: Re: Install and Uninstall Scripts


> "Michael A. Chase" <mchase AT ix DOT netcom DOT com> writes:
>
> > For uninstalls, I think it would probably work better if we agreed on a
> > naming convention for a script or batch file that would be executed
before
> > any packages are deleted.
>
> Yes, I thought about that too.  Or actually, to have the script
> executed before the specific package is deleted.
>
> I'm afraid that to solve this problem entirely, we would need
> preremove *and* postremove; and maybe something like Debian's purge.
>
> But as long as setup.exe does it's own package management, this is
> probably overkill; and I'd rather make a big improvement with a simple
> patch, than try to go all the way.
>
> The problem I wanted to solve (most) was for a package not to leave
> anything behind after uninstall.  That's why I would vote for
> postremove rather than preremove, and have it act like purge.  Maybe
> it would be acceptable for a package like ssh not to purge the host
> keys, but to delegate those things to /etc/postremove/cygwin.sh
>
> > Maybe something like /etc/preuninstall/package-version.{sh,bat}.
>
> Ok, my patch has something like /etc/postremove/package.{sh ? sh : bat}
> that would be ok then?