Date: Thu, 7 Feb 2008 23:01:28 +0100 From: Mel <fbsd.questions@rachie.is-a-geek.net> To: freebsd-questions@freebsd.org Cc: =?iso-8859-15?q?Micha=EBl_Gr=FCnewald?= <michael.grunewald@laposte.net> Subject: Re: Best practices for managing tweaked ports Message-ID: <200802072301.29261.fbsd.questions@rachie.is-a-geek.net> In-Reply-To: <86sl07y5fr.fsf@Llea.celt.neu> References: <86sl07y5fr.fsf@Llea.celt.neu>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,
On Tuesday 05 February 2008 13:05:12 Micha=EBl Gr=FCnewald wrote:
> I am seeking for a word in advice in how to automatically tweak some
> applications, possibly making packages for them.
>
>
> The current solution is: I have a post install shell script that plugs
> my files into appropriate location. This works but there is two
> drawbacks:
You're almost there:
=2D Create a file Makefile.local in the port you need a post-install shell=
=20
script executed with contents:
PKGINSTALL=3D/path/to/mycustomizations.sh
This will then be packaged in packages as well.
See pkg_create(1) and in particular -i option, as well as grep=20
_LATE_PKG_ARGS /usr/ports/Mk/bsd.port.mk
If you wanna do it cleaner, may want to wrap that in:
=2Eif !defined(PKGINSTALL) && !exists(${PKGDIR}/pkg-install)
=2E..
=2Eelse
error:
echo "Omg they killed kenny"
/usr/bin/false
=2Eendif
So that it errors out, if the port starts providing a post-install script.
=2D-=20
Mel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200802072301.29261.fbsd.questions>