From: andrea ferraris <andrea_ferraris@libero.it>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Conary
Date: Sun, 24 Oct 2004 13:28:49 +0200 [thread overview]
Message-ID: <417B91F1.7070909@libero.it> (raw)
In-Reply-To: <20041024093350.GB12337@gentoo.org>
Sven Vermeulen wrote:
> On Sat, Oct 23, 2004 at 10:18:56PM -0500, Ed Grimm wrote:
>
>>My issue is: Gentoo's patch system does not take current state into
>>account in any appropriate manner. This means that any file in /etc
>>which I have made changes will be updated improperly; I'll therefore
>>need to either throw out new changes or adapt them to my changes every
>>time Gentoo considers updating them.
>
>
> I don't think it's possible to magically update configuration files that you
> have altered and be able to tell you that the updated configuration file
> still is 100% functional.
100% maybe not, but actually the gentoo way is 0% and maybe between 0
and 100 there are some other figures ;-)
>>As an example, I'm not using the standard Gentoo partition layout. This
>>means that, every so often, Gentoo tries to "fix" my fstab.
>
>
> Ignore the update. There is no reason why you should update your /etc/fstab;
> unless you alter filesystems or partition layouts, /etc/fstab is static.
I did that most times, but why I have to do it?!
To avoid such annoyance it's not needed AI or grid computing, it's
enough Animal Intelligence ;-) anyway Scriptable Intelligence.
>>Other files which tend to be incredibly frustrating are basic config
>>files. For example, /etc/etc-update.conf. Every time an upgrade
>>decides it wants to check on the status of this file, it decides that,
>>on the whole, I was mistaken regarding my choice of difference viewer,
>>and the various other options I specified.
>
>
> You can interactively merge the changes. Most of the time, you can easily
> skim through the changes it proposes and decide that there is no need to
> merge them.
As said, but why I have to do that if most times it could be avoided by
means of a kind script?
Andrea
--
gentoo-portage-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-10-24 11:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 22:02 [gentoo-portage-dev] Conary andrea ferraris
2004-10-21 8:30 ` Paul de Vrieze
2004-10-21 9:52 ` Sven Vermeulen
2004-10-21 11:46 ` Roman Gaufman
2004-10-21 12:44 ` Sven Vermeulen
2004-10-21 13:20 ` Roman Gaufman
2004-10-21 13:52 ` Jason Stubbs
2004-10-24 17:44 ` andrea ferraris
2004-10-24 21:47 ` Roman Gaufman
2004-10-25 21:06 ` andrea ferraris
2004-10-21 19:00 ` Nathaniel McCallum
2004-10-21 19:19 ` Luke-Jr
2004-10-22 8:07 ` Paul de Vrieze
2004-10-22 11:24 ` Jason Stubbs
2004-10-22 13:11 ` John Nilsson
2004-10-22 13:21 ` Jason Stubbs
2004-10-22 13:31 ` Paul de Vrieze
2004-10-22 19:33 ` John Nilsson
2004-10-24 3:18 ` Ed Grimm
2004-10-24 9:15 ` Paul de Vrieze
2004-10-24 11:27 ` andrea ferraris
2004-10-24 20:52 ` Paul de Vrieze
2004-10-24 9:33 ` Sven Vermeulen
2004-10-24 11:28 ` andrea ferraris [this message]
2004-10-25 18:47 ` [gentoo-portage-dev] Conary - dispatch-conf LinuxGuy
2004-10-28 2:55 ` Ed Grimm
2004-10-28 17:18 ` LinuxGuy
2004-11-12 9:23 ` Ed Grimm
2004-11-28 20:15 ` LinuxGuy
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=417B91F1.7070909@libero.it \
--to=andrea_ferraris@libero.it \
--cc=gentoo-portage-dev@lists.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