From owner-freebsd-current@FreeBSD.ORG Fri Jun 4 23:30:51 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D990106567B for ; Fri, 4 Jun 2010 23:30:51 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3F9B98FC1B for ; Fri, 4 Jun 2010 23:30:50 +0000 (UTC) Received: by iwn5 with SMTP id 5so2002564iwn.13 for ; Fri, 04 Jun 2010 16:30:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=Prbdtj6tIHpVd269kgCIIw+w1hOOBEZXi7IcWXf4spc=; b=x3YAt0qcYe1jxTbu4NpJuBuQvoycRL2mjEPHSfi1gOzDH4g6fcBMOYYBmpecvV6SjJ bWce+WivP+fkN2JJTl8XsHWYN52ao2aew42I640EelaZegPFcuQ2MEDnJGZkKe8ePvnW KChjsZb6BQlKs4KmUqShLGL0Jz1TshqHvhdFM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=lZuFDnZoKY3PqBZm/at+If2GJtU1VkhIZPzewNcjH5R0P9NG96qUMsYcINNe1lNVHq /L7DWDpqCiZi/4a0nZYQqoz3Bqxd7PH/2qZpdKu9rAErC/Gui+j1ePFZwUpg0vjm/W96 xrcw4YIvVzDx2urku8TC33Nn5XMuLfmMHCtRE= MIME-Version: 1.0 Received: by 10.231.149.203 with SMTP id u11mr7780413ibv.6.1275694250351; Fri, 04 Jun 2010 16:30:50 -0700 (PDT) Received: by 10.231.16.137 with HTTP; Fri, 4 Jun 2010 16:30:50 -0700 (PDT) In-Reply-To: <4C0987A6.5010109@FreeBSD.org> References: <4C093E01.7020909@FreeBSD.org> <4C0987A6.5010109@FreeBSD.org> Date: Fri, 4 Jun 2010 16:30:50 -0700 Message-ID: From: Freddie Cash To: FreeBSD-Current Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: 'buildworld' not always pulling in /etc/src.conf X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jun 2010 23:30:51 -0000 On Fri, Jun 4, 2010 at 4:09 PM, Doug Barton wrote: > On 06/04/10 11:39, Freddie Cash wrote: > >> On Fri, Jun 4, 2010 at 10:55 AM, Doug Barton 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