public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Georgi Georgiev <chutz@gg3.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Interest Check: Dynamic config files for portage
Date: Wed, 2 Jul 2003 07:57:52 +0900	[thread overview]
Message-ID: <20030701225752.GF11227%chutz@gg3.net> (raw)
In-Reply-To: <20030701174923.35cefb97.kl4rkmail@jazzfree.com>

On 01/07/2003 at 17:49:23(+0200), Josep Sanjuas used 2.2K just to say:
> It'd also make portage easier to maintain, because for example, if
> I want to change the disftile or rsync mirrors then I can edit
> /etc/make.conf.f/fetch, or whatever its name would be, instead of finding the
> appropiate vars in the big make.conf.

So you'd actually have to find the appropriate vars in *all* those files. I'd
definitely not look in a file named "fetch" (since rsyncing hardly has anything
to do with fetching, considering what "emerge --fetch" does) for the means to
set my rsync server which only proves my point - you (or I if all gentoo devs
think like you) would first look in the wrong file. So every time I want to
change a var, I'll have to think where it might be in all those files.
Personally, I find looking for text in *one* file much easier when compared to
grepping a directory and THEN editing a file (and then running the tool to
mangle my files or "cat * > ../make.conf" or whatever).

-- 
 /   Georgi Georgiev    / He who is flogged by fate and laughs the      /
\     chutz@gg3.net    \  louder is a masochist.                       \
 /  +81(90)6266-1163    /                                               /

--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-07-01 22:57 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
2003-07-02  9:57         ` Toby Dickenson
2003-07-01 22:57     ` Georgi Georgiev [this message]
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=20030701225752.GF11227%chutz@gg3.net \
    --to=chutz@gg3.net \
    --cc=chutz-dated-1058309873.cd7a360642df@gg3.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