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.fried...@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.
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Reply via email to