Date: Sat, 9 Feb 2008 14:08:49 +0100 From: =?ISO-8859-1?Q?Micha=EBl_Gr=FCnewald?= <michael.grunewald@laposte.net> To: Mel <fbsd.questions@rachie.is-a-geek.net> Cc: =?ISO-8859-1?Q?Micha=EBl_Gr=FCnewald?= <michael.grunewald@laposte.net>, freebsd-questions@freebsd.org Subject: Re: Best practices for managing tweaked ports Message-ID: <C958B92A-E66C-43A2-87CA-6360C8F05402@laposte.net> In-Reply-To: <200802072301.29261.fbsd.questions@rachie.is-a-geek.net> References: <86sl07y5fr.fsf@Llea.celt.neu> <200802072301.29261.fbsd.questions@rachie.is-a-geek.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Le 7 f=E9vr. 08 =E0 23:01, Mel a =E9crit :
> 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 =20
>> plugs
>> my files into appropriate location. This works but there is two
>> drawbacks:
>
> You're almost there:
> - Create a file Makefile.local in the port you need a post-install =20
> shell
> 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
> _LATE_PKG_ARGS /usr/ports/Mk/bsd.port.mk
>
> If you wanna do it cleaner, may want to wrap that in:
> .if !defined(PKGINSTALL) && !exists(${PKGDIR}/pkg-install)
> ...
> .else
> error:
> echo "Omg they killed kenny"
> /usr/bin/false
> .endif
>
> So that it errors out, if the port starts providing a post-install =20
> script.
Thank you very much for the that tip!
It seems that this will fail for scripts that have `postinstall', or =20
more accurately, that changes may have to be versed in this =20
postinstall script, right?
--=20
Michi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C958B92A-E66C-43A2-87CA-6360C8F05402>