:-) I do not like to start flame, but ... in case u are so strong against scripts and tools, u have to use your own linux from scratch, because portage system is also such a tool on which everything starts and ends. U really can't say emerge is bugless ... do u ?
I also don't thing gentoo needs tools/scripts for everything ... just because KISS technology is still the more secure one. But in some cases if I compare pros and cons I wolud say, scripts are very usefull ...
Did u ever install qmail + vpopmail + courier-imap + spamassassin + lot of patches + lot of other tools on redhat from sources? If yes, u shell understand what I like to say.
I'll stop to use linux (not only gentoo) if the only way to configure it remains GUI clicker, but hope this never happens :-)
noro
SN wrote:
Well guys if you have a good solution, then bring it up to the developer, but writing a script for every shit and putting it into portage is not what I want, gentoo is still lean but mean, if you have problems with manually checking those kind of files after emerge, I think you are not using the right distro. I updated baselayout once, so I checked those files, I think it is no big deal, it even forces me to check if there were any changes or improvements.
As soon as gentoo starts to create scripts for any crap I switch again to another distro, the advantage of not having tools for anything is, that those tools can't break. Look at Suse RedHat Mandrake, 30% of their bugs come from the tools they wrote.
----- Original Message ----- From: "Norbert Kamenicky" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, January 01, 2004 6:53 PM
Subject: Re: [gentoo-user] Base layout causing pointless config updates
SN wrote:
----- Original Message ----- From: "Andy Arbon" <[EMAIL PROTECTED]>
To: "gentoo-user" <[EMAIL PROTECTED]>
Sent: Tuesday, December 30, 2003 6:38 PM
Subject: [gentoo-user] Base layout causing pointless config updates
Hello,
I'm just wondering if anyone here knows if anything is being done with etc-update or the baselayout package to stop it pointlessly trying up update a load of configuration files that I'm never going to let it touch every time it is updated?
It seems like baselayout's changed quite regularly recently (this is in the x86 branch) and every time it does I get asked to update: 1) /etc/DIR_COLORS 2) /etc/devfsd.conf 3) /etc/fstab 4) /etc/group 5) /etc/passwd 6) /etc/rc.conf 7) /etc/shadow 8) /etc/conf.d/net 9) /etc/modules.autoload.d/kernel-2.6
Aside from rc.conf and maybe devfsd.conf I can't think of a single one of those that should ever be replaced or merged with a vanilla copy. In fact with most of them accidentally replacing the file with a vanilla one would be somewhere between an annoyance and a major headache.
What if baselayout introduces a new group or user???? Think about it.
In that case it should be done by script, which at first checks the presence of the new user and then adds it to the copy of existing system passwd file (if necessary).
I am sorry, but I thing, that adding a new user by replaceing passwd file with new uniform passwd file (from baselayout), which do not fit to any configured system (except of just installed one) is a the most stupid way how it can be done. And I am sure that it's not only my opinion.
Happy New Year to everybody!
noro
-- [EMAIL PROTECTED] mailing list
-- [EMAIL PROTECTED] mailing list
-- [EMAIL PROTECTED] mailing list
