how to tell pkg-list not to deinstall/overwrite certain files

Aryeh Friedman aryeh.friedman at gmail.com
Sun Nov 10 04:59:14 UTC 2013


Thanks the stuff worked there but it is not clear how to handle user dirs
(don't nuke dirs withi user data for example we create /usr/local/vms and
it should not be erased on deinstall)


On Fri, Nov 8, 2013 at 6:13 AM, Tijl Coosemans <tijl at coosemans.org> wrote:

> On Fri, 8 Nov 2013 05:23:47 -0500 Aryeh Friedman wrote:
> > Forgot to mention the solution should if at all possible be 100%
> pkg-plist
> > based because our internal build system is not make
> >
> > On Fri, Nov 8, 2013 at 5:21 AM, Aryeh Friedman <aryeh.friedman at gmail.com
> >wrote:
> >> I am doing a lot of inter-machine testing of a private port (will be
> >> released soon as a actual port) but need to tell "make deinstall" not to
> >> delete a certain file... how do we do this?... background one thing we
> are
> >> testing is the ability to upgrade the port (privately) and it must not
> nuke
> >> our settings file on the test machines because the default config
> provided
> >> by our port is inappropriate for how we have things configured (it is
> >> correct for 99.9% of everyone else though).
> >>
> >> Namely we need:
> >>
> >> 1. Do not delete  /usr/local/etc/petitecloud/settings on deinstall
> >> 2. Do not overwrite it with a new version on install (if present else
> >> install it)
>
> Basically you have to install the file as settings.sample and add some
> pkg-plist magic.  It's explained in more detail here:
>
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/plist-config.html
>
> Note that with staging you don't need the post-install part, only the
> pkg-plist part.
>


More information about the freebsd-ports mailing list