Date: Fri, 4 Jun 2010 16:30:50 -0700 From: Freddie Cash <fjwcash@gmail.com> To: FreeBSD-Current <freebsd-current@freebsd.org> Subject: Re: 'buildworld' not always pulling in /etc/src.conf Message-ID: <AANLkTilcJPcJ4JsW5Lzw0ikMZOLUlAAAI_NeZpMjd1E_@mail.gmail.com> In-Reply-To: <4C0987A6.5010109@FreeBSD.org> References: <AANLkTikA4QPoT0e540nCSc0_LAAycIjAOQOGLB-e2BjY@mail.gmail.com> <op.vdojtep843o42p@klevas> <AANLkTilsDmdbqIELw3SkSlOZQ-WzlLjg1bgs2-WhSAQf@mail.gmail.com> <4C093E01.7020909@FreeBSD.org> <AANLkTikdmzgaFgZdMWznWBDWKb_8_Oak1p3Hb41ruTuR@mail.gmail.com> <4C0987A6.5010109@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 4, 2010 at 4:09 PM, Doug Barton <dougb@freebsd.org> wrote:
> On 06/04/10 11:39, Freddie Cash wrote:
>
>> On Fri, Jun 4, 2010 at 10:55 AM, Doug Barton<dougb@freebsd.org> wrote:
>>
>> Wouldn't it be great, if /etc/make.conf disappeared completely?
>>
>
> No, since it's useful for things that are common to both src and ports, and
> to stuff that is neither.
make.conf could be reserved for "normal", non-buildworld, non-ports-related
stuff, when one just runs make by itself (ie, a config file for make), for
one's own uses.
src.conf could be for stuff that only matters to
buildworld/kernel/universe/etc (just stuff under /usr/src). IOW, a config
file for the source tree builds.
ports.conf could be for stuff that only matters to ports building (just
stuff under /usr/src). IOW, a config file for the ports tree.
Seems silly to have a separate src.conf without a separate ports.conf, as
the requirements for them are very different.
I had a long, multi-page spec for this written up (gotta love insomnia), but
/etc/src.conf appeared while it was still in draft form, so I never
finished/submitted it. Sounded like this was the direction things were
heading, so I never thought about it further.
ports-mgmt/portconf.
portconf has horrible syntax, compared to make.conf/src.conf, at least last
I tried to use it (when it first came out). And this is geared more toward
per-port configuration settings. ports.conf would be for global settings
for the whole ports tree, stuff that affects multiple ports. Things like
WITH{OUT}_X11, WITH{OUT}_GNOME, CPUTYPE, perl version info, selecting a
default python version, etc.
Of course, if it's grown those features (global ports settings), then this
whole discussion is moot, as one can just ignore make.conf, and use
src.conf/portconf config file.
--
Freddie Cash
fjwcash@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTilcJPcJ4JsW5Lzw0ikMZOLUlAAAI_NeZpMjd1E_>