public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Owen Gunden <ogunden@stwing.upenn.edu>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Interest Check: Dynamic config files for portage
Date: Tue, 1 Jul 2003 18:29:29 -0400	[thread overview]
Message-ID: <20030701222928.GA23646@force.stwing.upenn.edu> (raw)
In-Reply-To: <200307011732.56525.tdickenson@devmail.geminidataloggers.co.uk>

On Tue, Jul 01, 2003 at 05:32:56PM +0100, Toby Dickenson wrote:
> On Tuesday 01 July 2003 16:49, Josep Sanjuas wrote:
> 
> > I think there could be more advantages.
> 
> they dont seem very compelling.....

There is one compelling advantage that I believe was intended by the
original poster.  That is this: in the current situation, when I upgrade
baselayout I get a new make.conf which I have to merge by hand.  In my
experience this is definitely the hardest file in /etc to merge because of
its size and the amount of customization I've done to it.  If it were split
into separate files, it would be easier to see where the new stuff is.
Also, I would be familiar with the particular sections that I'd made
changes to, so I could simply copy the maintainers version of any files
that I know I haven't changed.

I may be a special case, though; I can't use etc-update because it has IMHO
a horrendous interface.  

I'm skeptical about a configuration tool to fix make.conf automatically,
because I've seen so many such things go wrong.  On the other hand, ufed is
indispensible, and if such a utility were as easy-to-use and
easy-to-know-what-it's-doing as ufed I would definitely consider using it.

Owen
searching his pockets for 2 pennies..

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-07-01 22:29 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-01  9:58 [gentoo-dev] Interest Check: Dynamic config files for portage Seemant Kulleen
2003-07-01 10:32 ` Ferris McCormick
2003-07-01 10:35 ` Rigo Ketelings
2003-07-01 10:46 ` [gentoo-dev] " sf
2003-07-01 11:28 ` [gentoo-dev] " Georgi Georgiev
2003-07-01 11:34 ` Lisa M.
2003-07-01 12:12 ` Stewart Honsberger
2003-07-01 13:41 ` Troy Dack
2003-07-01 14:07   ` Lisa M.
2003-07-01 14:27   ` William Kenworthy
2003-07-01 15:37     ` Alex Veber
2003-07-01 22:25     ` Troy Dack
2003-07-01 22:49   ` Georgi Georgiev
2003-07-01 14:05 ` Toby Dickenson
2003-07-01 15:49   ` Josep Sanjuas
2003-07-01 16:32     ` Toby Dickenson
2003-07-01 22:29       ` Owen Gunden [this message]
2003-07-02  9:57         ` Toby Dickenson
2003-07-01 22:57     ` Georgi Georgiev
2003-07-01 14:12 ` Dhruba Bandopadhyay
2003-07-01 18:13   ` Svyatogor
2003-07-01 14:49 ` Svyatogor
2003-07-02  0:40 ` Robert Bragg
2003-07-02  2:56 ` Aron Griffis
2003-07-02  3:03   ` Aron Griffis
2003-07-02  3:51   ` Grant Goodyear
2003-07-03  5:36     ` Kumba
2003-07-03  6:04       ` Owen Gunden
2003-07-04 14:12 ` Spider
2003-07-04 23:38   ` Troy Dack
2003-07-05 17:38 ` Devdas Bhagat

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=20030701222928.GA23646@force.stwing.upenn.edu \
    --to=ogunden@stwing.upenn.edu \
    --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