Date: Tue, 13 Sep 2011 08:31:10 +0100 From: Chris Rees <utisoft@gmail.com> To: Gerald Pfeifer <gerald@pfeifer.com> Cc: ports@freebsd.org, Wesley Shields <wxs@freebsd.org>, Doug Barton <dougb@freebsd.org>, Emanuel Haupt <ehaupt@freebsd.org> Subject: Re: How to best run a script post installation _and_ deinstallation? Message-ID: <CADLo839QbiZdgy3_6-2=1Hf4qaUda%2BGvYAk0UAZmjwA3_ogAAQ@mail.gmail.com> In-Reply-To: <alpine.LNX.2.00.1109130215500.3106@gerinyyl.fvgr> References: <alpine.LNX.2.00.1105222256250.13877@gerinyyl.fvgr> <20110523130954.GB71868@atarininja.org> <alpine.LNX.2.00.1109130215500.3106@gerinyyl.fvgr>
next in thread | previous in thread | raw e-mail | index | archive | help
On 13 Sep 2011 01:36, "Gerald Pfeifer" <gerald@pfeifer.com> wrote: > > On Sun, 22 May 2011, Doug Barton wrote: > > Will @unexec in pkg-plist do the job? > > On Mon, 23 May 2011, Wesley Shields wrote: > > Are these what you are looking for: > > > > http://www.freebsd.org/doc/en/books/porters-handbook/pkg-install.html > > http://www.freebsd.org/doc/en/books/porters-handbook/pkg-deinstall.html > > Yes and no (to both questions). > > I have been looking for a silver bullet that avoids having > (a) something in the post-install target plus an @exec and an @unexec > and thus redundancy, or > (b) two extra scripts and thus two extra files in the port. > > Alas, I failed at that, and Emanuel convinced me that apparently there > is no way to avoid one of these two deaths. > > That looks like a nice project for someone to improve our general > infrastructure along these lines. > Most people faced with this problem redefine PKGDEINSTALL to the location of the pkg-install script. Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo839QbiZdgy3_6-2=1Hf4qaUda%2BGvYAk0UAZmjwA3_ogAAQ>