Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 10 Apr 2006 14:55:55 +0200
From:      Alexander Leidinger <Alexander@Leidinger.net>
To:        Thierry Thomas <thierry@freebsd.org>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: BEWARE upgrading Horde System
Message-ID:  <20060410145555.291wa5oc0s04gko0@netchild.homeip.net>
In-Reply-To: <20060410075351.GA40925@graf.pompo.net>
References:  <20060407032220.W947@ganymede.hub.org> <1144391457.23833.6.camel@shumai.marcuscom.com> <44363371.9050200@fromley.net> <20060407141831.GA65673@pentarou.parodius.com> <20060408075305.GB58919@graf.pompo.net> <20060409050018.X1096@ganymede.hub.org> <20060409201012.GF93845@graf.pompo.net> <20060409203111.S1096@ganymede.hub.org> <20060410075351.GA40925@graf.pompo.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Thierry Thomas <thierry@freebsd.org> wrote:

> Le Lun 10 avr 06 =C3=A0  1:41:59 +0200, Marc G. Fournier <scrappy@hub.org>
>  =C3=A9crivait :

>> You've missed the 3rd, and optimal, option: on initial install, install
>> the config files based on the .dist files, but *do not* overwrite an
>> existing config file (ie. after an upgrade) ...
>
> If you want the package to install these files, they must be registered
> in pkg-plist, and then they will be deinstalled.

Several ports already handle this situation. There's some "plist =20
magic" which does a "@exec [ -e x ] || cp x.dist x" (or something like =20
this, I didn't looked it up) and a "@unexec cmp x.dist x <appropriate =20
conditional> rm x".

So it makes a copy to the config file from the .dist one on =20
installation and removes the config if it is equal to the .dist one on =20
deinstallation. It may be the case that you have to do the same thing =20
in the port Makefile too (when @exec isn't executed when installing =20
from source). Another alternative would be a pkg-(de)install script =20
which handles the removal in the pre-deinstall case and the copy in =20
the post-install case.

While we're discussing the horde upgrade... is there some trick to run =20
the 3.0 to 3.1 history migration script or is my php setup fucked-up =20
in the CLI (for the apache module case everything is setup in =20
httpd.conf, no php.ini) case (I get some error messages about not =20
being able to include pear.php or something like this... I don't have =20
the error messages at hand)?

Bye,
Alexander.

--=20
http://www.Leidinger.net  Alexander @ Leidinger.net: PGP ID =3D B0063FE7
http://www.FreeBSD.org     netchild @ FreeBSD.org  : PGP ID =3D 72077137
  Leela: Your face can take a lot of punishment. That's good to know.
  Fry: There's a lot about my face you don't know.





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060410145555.291wa5oc0s04gko0>