From: Alexander Gretencord <arutha@gmx.de>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-user] "etc-update" versus Manual update opinions..
Date: Wed, 17 Sep 2003 19:09:53 +0200 [thread overview]
Message-ID: <200309171909.53290.arutha@gmx.de> (raw)
In-Reply-To: <F4DE20B2-E91F-11D7-9EE5-000A95795F3E@stellar.eclipse.co.uk>
On Wednesday 17 September 2003 17:02, Stroller wrote:
> On 17 Sep 2003, at 1:24 pm, Gwendolyn van der Linden wrote:
> > brett holcomb [mailto:brettholcomb@charter.net] wrote:
> >> Well, if you use etc-update on files like /etc/fstab your
> >> system will break.
No it doesn't break, it just breaks if you foolishly hit "just overwrite all
files with the new version".
> > Exactly. I would vote for keeping /etc/fstab.example in portage, and
> > making the copying/editing part of the installation procedure (cp
> > /etc/fstab.example /etc/fstab; nano -w /etc/fstab).
> I agree. I wouldn't be surprised if this was changed, were you to file
> it as a bug. I'm cross posting to gentoo-dev to see what they think.
I wouldn't be if it wouldn't. I would really like this to be consistent in
gentoo. Syslog-ng has a syslog-ng.sample file, postfix has many sample files,
many other packages don't and you got to use etc-update. Well sometimes I
really welcome etc-update and config file merging and on other occasions it
just sucks and is a pain in the ass. Difficult decision I'd say.
Alex
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-09-17 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OLEMJKKJBJMMNIPIEKLLGENIDBAA.Gwendolyn.van.der.Linden@technolution.nl>
2003-09-17 15:02 ` [gentoo-dev] Re: [gentoo-user] "etc-update" versus Manual update opinions Stroller
2003-09-17 15:46 ` Chris Gianelloni
2003-09-17 17:09 ` Alexander Gretencord [this message]
2003-09-17 18:11 ` John Mylchreest
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=200309171909.53290.arutha@gmx.de \
--to=arutha@gmx.de \
--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