From: "Troy Dack" <tad@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Interest Check: Dynamic config files for portage
Date: Wed, 2 Jul 2003 08:25:34 +1000 (EST) [thread overview]
Message-ID: <45202.203.10.231.229.1057098334.squirrel@tkdack.bpa.nu> (raw)
In-Reply-To: <1057069671.21908.18.camel@rattus.Localdomain>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'll state now that I like the idea of multiple files.
Bill K wrote thusly ...
> This is the reason that ufed has become so popular, and I think
> necessary - the complexity is getting too much.
For USE flags the complexity has increased, mainly because the number of
USE flags has grown and it's not possible to remember every single flag
and what effect it is going to have on building of packages.
> Would a ufed like utility for make.conf be a better approach?
I really don't like the idea of YAGU (Yet Another Gentoo Utility). I
really like the fact that I can just edit the text files and I don't need
to start up a utility to do it.
The other reason I don't like YAGU is that someone will have to write it
and maintain it, this is not a trivial task as changes to portage will
eventually have some impact on how the utility is written and performs.
> 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.
OK, about the only time that you will have to edit many files in turn is
during the initial installation process. Personally I don't think that
this is a bad thing, if the documentation is accurate then the
installation process (editing the files) is an excellent educational
experience for new users.
This issue was initially raised due to the fact that a small change to
/etc/make.conf and then merging those changes using etc-update gets very
tiresome. Generally the changes are simply to the comments and the
comments of only one section. By having multiple files then only one file
(section) will be touched and you don't have to worry about the other 250
lines. [not having looked but could/can the "Merging trivial updates..."
stage of etc-update handle merging these comments?]
- --
Troy Dack
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/AgpU/YkW+U2QvjwRAmiNAJwPx5STl3I8TW64n7tKHUpjeZv5SACgjg75
DtaaavUwXgeEfcgne01gaBA=
=IHun
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-07-01 22:25 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 [this message]
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=45202.203.10.231.229.1057098334.squirrel@tkdack.bpa.nu \
--to=tad@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