[lug] what would break if...
stimits at idcomm.com
Sun May 19 01:27:04 MDT 2002
Sean Reifschneider wrote:
> On Fri, May 17, 2002 at 02:51:44PM -0600, D. Stimits wrote:
> >including rpm itself, along with some other important packages (like
> >pam...break that and watch the system die). The funny thing is that one
> >of the packages that needs it is php-4.0.6, but I want to upgrade db3 to
> >get php 4.1. I think whoever coined the phrase "dependency hell" will go
> Why don't you just do an upgrade to 7.3 and be done with it? 7.3 includes
> packages built against db3.3, so it'll just work...
There would be some humor in that: A package to install something like
an email package, that starts by quietly upgrading the whole system to
RH 7.3. Advertisement: "This works on all semi-recent versions of
Redhat". The goal is to do some packaging that makes this work on
ordinary RH 7.x, without regard to .x.
> Otherwise, remove any packages that you can which depend on the older db,
> keep a copy of /usr/bin/rpm around, and try forceing the install of the db
> RPM, then start re-building everything that it was complaining about from
> SRPMs. This will work, if for some reason you really can't just let the
> Red Hat folks do all this for you.
Messing with the possibility of breaking my rpm database on my real
working machine is a bit scarey. Messing with someone else's system and
breaking it is even scarier.
> I did something similar to this years ago with a 5.2 box that I couldn't
> easily upgrade and gtk. Once you've done it, you're pretty well limited to
> building packages from SRPMs, which isn't really so bad.
Wouldn't be so nice though, if you installed someone else's package, and
without your knowledge, it updates rpm such that from then on you need
srpms. It's that "stuck between a rock and a hard place" feeling right
D. Stimits, stimits at idcomm.com
More information about the LUG