From: Alex Veber <coronalvr@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Interest Check: Dynamic config files for portage
Date: Tue, 1 Jul 2003 18:37:58 +0300 [thread overview]
Message-ID: <200307011838.12567.coronalvr@gentoo.org> (raw)
In-Reply-To: <1057069671.21908.18.camel@rattus.Localdomain>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday 01 July 2003 17:27, William Kenworthy wrote:
> This is the reason that ufed has become so popular, and I think
> necessary - the complexity is getting too much. Would a ufed like
> utility for make.conf be a better approach? I am not so keen on
> spawning a number of small bit files for a make.cond.d as that does not
> fix the managebility issue - you will have to edit many files in turn,
> instead of just one file every time.
>
> BillK
>
> On Tue, 2003-07-01 at 21:41, Troy Dack wrote:
> > Seemant Kulleen wrote:
> > >Hi All,
> > >
> > >Before I go and invalidate a bug, I thought I might take the idea around
> > > here to see if it has any merit in terms of usefulness/interest.
> > >
> > >The idea stems from the fact that etc-updating a make.conf file can be a
> > > bit of a stressful event. And as portage's set of features grows, so
> > > too will the size of the make.conf file. I get the impression that the
> > > make.conf file is a little hard to parse, with the huge comment blocks
> > > etc etc. So my proposal is this: a make.conf.d directory which
> > > contains files for each section of the make.conf: use, flags, fetch,
> > > packagevars.
> >
> > Nice idea, something that I have thought about before.
>
> --
> gentoo-dev@gentoo.org mailing list
splitting make.conf to many files is not a solution.
imho we should create a tool to parse make.conf and change it.
that way we leave the choice to the user on how to modiffy his settings.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/Aara0Q5UUdinJT4RAv86AKDawnH25KeJBNHTQc9kmA5kSM75AwCgzlS0
kCvCMlFYrwtsrS9Wkov6pC8=
=fCXa
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-07-01 15:28 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 [this message]
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
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=200307011838.12567.coronalvr@gentoo.org \
--to=coronalvr@gentoo.org \
--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