On Tue, 5 Sep 2006, seth vidal wrote:
On Tue, 2006-09-05 at 17:26 -0400, Christopher Aillon wrote:
seth vidal wrote:
On Tue, 2006-09-05 at 16:59 -0400, Christopher Aillon wrote:
Panu Matilainen wrote:
The fix is to either 'rpm -e yum-versionlock' if you don't use it or to
provide the missing config file.
I'm guessing he performed an "everything" install, whatever that means
these days. So it sounds like there should be a config provided with
it. Making the default system unusable is plain silly, especially since
it would also mess with the applet.
you're thinking like a user and not like a sysadmin.
Then there is clearly a problem in yum or anaconda or maybe even rpm for
not determining whether the person installing the package is a user or a
sysadmin.
If that file went missing it would screw up a lot of systems that are
locked in.
I don't doubt that. Perhaps this specific plugin should be disabled by
default then even after install. e.g. enabled = 0 in versionlock.conf
instead of enabled = 1. And just require the user^H^H^H^H sysadmin
explicitly turning it on (they already have to do work to make the
plugin useful, what's one more step?)
doesn't bother me if that's the case.
Panu?
No problem with that - in fact now that these things are packaged that's
the way it *should* be. IIRC the original reason for it being enabled=1 by
default is that it was something people would be manually digging out of
yum-utils docdir instead of being just yum install away.
Fedora is not just for end users in front of laptops.
That doesn't mean we can screw the end user for the benefit of the
sysadmin, or vice versa.
I think discouraging 'everything' installs by aversion therapy might be
a good idea, though. :)
Heh. Anyway, changed the default behavior in cvs now, with some regrets
due to making life easier for people doing everything-installs :)
- Panu -
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
