Date: Wed, 13 Oct 2004 18:34:29 -0400 From: "Frank J. Laszlo" <laszlof@vonostingroup.com> To: Sebastian Schulze Struchtrup <seb@struchtrup.com> Cc: freebsd-ports@FreeBSD.org Subject: Re: alternative options for ports Message-ID: <416DAD75.7000504@vonostingroup.com> In-Reply-To: <416DAB52.5070404@struchtrup.com> References: <416C0DE8.3000004@struchtrup.com> <416C35A5.4040703@vonostingroup.com> <20041013123840.GB1301@FreeBSD.org> <20041013193432.GA53895@hub.freebsd.org> <416DAB52.5070404@struchtrup.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>
>> Since we go to a *lot* of work building packages and making them
>> available there must be a huge number of consumers of them. We
>> should be
>> making more port variations. vim-gtk, vim-kde, vim-athena, vim-motif
>> for
>> instance. That way a pkg_add user and get what they want.
>>
>>
> I assume that this is currently done by hand? To say build the vim
> port with options --with-gtk, --with-kde and --with_arena?
> Or is there a way to set this in a Makefile? Not only altering the
> package name from vim to vim-xxx, but to define configurations for
> automatic package building?
using vim as an example, currently the port recognises env variables
like most other ports do. e.g. WITH_GTK2, WITH_ATHENA etc.. these
generally make changes to the CONFIGURE_ARGS. Regarding package
building, there is an option (with the vim port) for PACKAGE_BUILDING
which builds with the most common options. I'm not exactly sure what
kind of answer you were looking for, but just my little input on the
subject :)
Regards,
Frank
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?416DAD75.7000504>