On Dec 22, 2005, at 5:37 PM, Tim Mooney wrote:
In regard to: Re: rpm installation inside another rpm - database
locked...:
Ever hear the term "dependency hell"? The (or one) solution is to
bundle constructs like "GNOME" or "KDE" or "JAVA" or "BASE" or
whatever else,
and install as a single bundled rpm.
The person that I learned RPM from all those years ago does this,
to this
day. For small, light distributions it's ok, but I've never been very
fond of it. For one thing, if "Base" includes pieces from 25 separate
packages and one of them needs to be updated to fix a security
issue, you
have a lot greater chance of introducing incompatibilities by
installing
the next release of Base, because you're essentially upgrading
everything.
I understand why people might choose this route, but it's not without
its own problems.
Replacement of a single item like, say, util-linux*.rpm within a
bundle is far far easier
to manage (and QA) than slopping the new stuff into a rawhide repo and
letting users sort it out.
You do realize that the "single" option passed to /etc/init was just
borked by
throwing untested upgrades into FC5 test2? This week's fedora-devel fun.
If you can't do the QA, no amount of packaging is gonna save you. Ever.
Meanwhile "bundles" (my term) or "components" (Progeny's) simplify
the QA by layering, just like any good unit -> integration -> system
testing methodology. It's easier to spot flaws if there are fewer
objects
with less complicated data.
73 de Jeff
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
