public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Harring <bdharring@wisc.edu>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] etc-update
Date: Sun, 13 Apr 2003 04:57:20 -0500	[thread overview]
Message-ID: <200304130457.20196.bdharring@wisc.edu> (raw)

While I'm on an emailing spree, anyone got any ideas on how to make etc-update 
a bit less painful?
It seems like a lot of the times where etc-update requires user intervention 
it's fairly minor- case in point, make.conf, when the default/base-layout 
make.conf gets updated.  It seems like it usually chokes on configured 
options, features or gentoo_mirrors as an example.

What if we were to either A) maintain a listing of default conf files (when 
modifying/adding a conf file, make.conf again, store it somewhere), or B) 
pull the conf from the distfile in some way?  The reason I ask is it strikes 
me if etc-update where able to compare the old default conf against the 
current conf it might be able to create a diff it could use to patch against 
the new one.  A bit wordy, but basically I'm wondering if we could isolate 
the changes a user has made, and attempt to merge those changes into the new 
conf file via a diff.
The problem I see with this would be that where (say GENTOO_MIRRORS) gets 
updated to some new default setting, the generated diff wouldn't be able to 
match against the new conf.
Thoughts?
~harring
bdharring@wisc.edu

--
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2003-04-13 10:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-13  9:57 Brian Harring [this message]
2003-04-13 16:07 ` [gentoo-dev] etc-update Jon Portnoy
  -- strict thread matches above, loose matches on Subject: below --
2003-03-07 21:19 Balaji Srinivasan
2003-03-08  3:57 ` Michael Kohl
2003-03-07 21:13 Martin, Stephen

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=200304130457.20196.bdharring@wisc.edu \
    --to=bdharring@wisc.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