Subject: Re: per package CONFIGURE_ARGS in mk.conf
To: diro@nixsys.bz <diro@nixsys.bz>
From: Julio M. Merino Vidal <jmmv84@gmail.com>
List: tech-pkg
Date: 11/04/2006 20:03:10
On 11/4/06, diro@nixsys.bz <diro@nixsys.bz> wrote:
> >> On Fri, Nov 03, 2006 at 07:51:02PM +0000, diro@nixsys.bz wrote:
> >> Is there an easy way to specify CONFIGURE_ARGS for different packages in
> >> mk.conf?
>
> > You shouldn't do that, but it can be done by using ${.CURDIR}.
>
> > Joerg
>
> There are options i need to feed the mail/sqwebmail build, which aren't
> covered in its PKG_OPTIONS. Rather then edit the Makefile, update via CVS
> every quarter and deal with the mangled Makefile, i've found it easier to
> just remove the whole tree and replace it anew each quarter. Instead of
> re-editing the Makefile for certain packages, i was hoping there's an easier
> way to feed it specific options.
>
> What would be so horrible about having something like
> CONFIGURE_ARGS.package_name? This would save having a lot of PKG_OPTIONS
> settings for the many configure args that can be used to tweak specific
> packages.

That many configure options have lots of side effects with respect to
installed files, available features, program behavior, etc.
Supporting such a setup would result in lots of random problems and
broken packages all around.

On the other hand, the existing PKG_OPTIONS have (supposedly) been
tested and the package is properly made to honor them (registering the
correct files, keeping track of dependencies appropriately, etc.).

-- 
Julio M. Merino Vidal <jmmv84@gmail.com>
The Julipedia - http://julipedia.blogspot.com/