public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: "C. Brewer" <cbrewer@stealthaccess.net>
Cc: Gentoo-Dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] make.conf
Date: Sun, 07 Sep 2003 12:46:58 +0200	[thread overview]
Message-ID: <1062931618.8455.78.camel@nosferatu.lan> (raw)
In-Reply-To: <20030906231736.3347b648.cbrewer@stealthaccess.net>

[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]

On Sun, 2003-09-07 at 08:17, C. Brewer wrote:
>  I was thinking that it might be nicer to do 2 files instead of the one.
> granted it's not too much trouble to do an interactive merge, and since my
> .nanorc is runs it so comments are colored, I really have no trouble picking
> out what I don't have commented. However, I see a real benefit to having a
> make.conf and make.conf.example (ala lilo,prozilla,etc.) so that the
> operator could have their six or seven line make.conf, only overriding the
> usual functions (CFLAGS,mirrors,PORT_OVERLAY,etc.) This would make it so
> that the make.conf.example could be auto-updated, and then those interested
> in playing with their make.conf could just periodically browse the
> make.conf.example to see if any new features have been added. Also, I seem
> to recall the when new user-affecting feature get added, there's usually
> some sort of announce here, so you really wouldn't need to look at it unless
> you see something here. I think this solution would provide amiable results
> for both camps:)

As I said in another post, I am still using a make.conf on some of
my systems that was originally from portage 1.8 or there abouts.
As long as you keep make.globals up to date, it should not be an
issue.


-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-09-07 10:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-07  6:17 [gentoo-dev] make.conf C. Brewer
2003-09-07 10:46 ` Martin Schlemmer [this message]
2003-09-08  6:35   ` C. Brewer
     [not found] <000a01c1a6f6$647688a0$0200a8c0@mike1>
2002-01-27  6:11 ` Chad M. Huneycutt
  -- strict thread matches above, loose matches on Subject: below --
2001-04-19  4:04 BoehmeSilvio
2001-04-19  9:19 ` Daniel Robbins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1062931618.8455.78.camel@nosferatu.lan \
    --to=azarah@gentoo.org \
    --cc=cbrewer@stealthaccess.net \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox