from the quill of Axalon Bloodstone <[EMAIL PROTECTED]> on scroll
<[EMAIL PROTECTED]>
> On Mon, 21 Feb 2000, Brian J. Murrell wrote:
>
> well yeah libgtop won't install..
And things that need libgtop won't work because 1.1.3 will not be
installed either.
> No. First off I never said to use nodeps.
No you didn't. Somebody else did though. Did not mean to infer you
did, sorry.
> You want to install it along
> side of the older version, breaking as little as posible in the mean
> time.
Why even bother though? Why not wait for the rest (i.e. the dependant)
of the packages to catch up?
> If you use nodeps you do not get told about the missing file
> (tracking it down now) in libgtop-1.1.5-0.1mdk
> (libgtop_sysdeps-1.1.so.5),
> it would be pretty much useless
OK, another problem with it. :-)
> > What happens if you force 1.1.5 on and then remove 1.1.3? Does any
> file
> > that is the same name in both packages get removed with the 1.1.3
> > removal or is RPM smart enough to know that a given file, that was
> in
> > 1.1.3 and then overwritten by 1.1.5 should not be removed when 1.1.3
> is
> > removed (with rpm -e)?
> >
> > b.
>
> You shouldn't have to force it, you would issue
[ snip ]
> Once all the files linked to older libs are updated, you issue
>
> rpm --test -evv libgtop-1.1.3-Xmdk
> # Remove the obsolete libs
>
> Rpm will skip over the "common/newer" files when you erase the older
> rpm.
Really? Holy smackers RPM is good!
> Bon?
Oui! Tres bon!
Merci beaucoup!
b.
--
Brian J. Murrell InterLinx Support Services, Inc.
North Vancouver, B.C. 604 983 UNIX
Platform and Brand Independent UNIX Support - R3.2 - R4 - BSD
