Re: [Cooker] Re: libgtop-1.1.5-0.1mdk

2000-02-21 Thread Axalon Bloodstone

On Mon, 21 Feb 2000, Brian J. Murrell wrote:

> from the quill of Axalon Bloodstone <[EMAIL PROTECTED]> on scroll
> <[EMAIL PROTECTED]>
> > 
> > Yep. it's time for the month long rebuilding of gnome, goes from David
> > to
> > pablo to me and back and forth between me and pablo for the rest,
> > takes
> > awhile to get it all rebuilt.
> 
> OK.  Should any RPMs get cut until it is all ready to go then?  I mean
> if somebody were to burn a CD from Cooker today they would have
> troubles.

well yeah libgtop won't install..
 
> > In the mean time either don't use -U (use
> > -i), or don't pay attention to gnome stuff for a couple weeks :)
> 
> Well the only choice really is the latter, no?  The issue of using -i
> and not using -U is only one of getting the package to actually install.
>  Once you do install it (using -i --nodeps), you will break everything
> that wants libgtop won't you?  Or will the two versions of the libraries
> live together on the box, while all of the common files (like share,
> doc, etc.) will get overwritten by the new version?

No. First off I never said to use nodeps. You want to install it along
side of the older version, breaking as little as posible in the mean
time. 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
 
> 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

rpm --test -ivv --replace-files libgtop-1.1.5-0.2mdk.i586.rpm
# install 1.1.5 overwriteing any common files

rpm --test -Uvv libgtop-devel-1.1.5-0.2mdk.i586.rpm
# replace the old devel with the new

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. 

Bon?

-- 
MandrakeSoft  http://www.mandrakesoft.com/
--Axalon



Re: [Cooker] Re: libgtop-1.1.5-0.1mdk

2000-02-21 Thread Brian J. Murrell

from the quill of Axalon Bloodstone <[EMAIL PROTECTED]> on scroll
<[EMAIL PROTECTED]>
> 
> Yep. it's time for the month long rebuilding of gnome, goes from David
> to
> pablo to me and back and forth between me and pablo for the rest,
> takes
> awhile to get it all rebuilt.

OK.  Should any RPMs get cut until it is all ready to go then?  I mean
if somebody were to burn a CD from Cooker today they would have
troubles.

> In the mean time either don't use -U (use
> -i), or don't pay attention to gnome stuff for a couple weeks :)

Well the only choice really is the latter, no?  The issue of using -i
and not using -U is only one of getting the package to actually install.
 Once you do install it (using -i --nodeps), you will break everything
that wants libgtop won't you?  Or will the two versions of the libraries
live together on the box, while all of the common files (like share,
doc, etc.) will get overwritten by the new version?

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.


--
Brian J. Murrell  InterLinx Support Services, Inc.
North Vancouver, B.C. 604 983 UNIX
Platform and Brand Independent UNIX Support - R3.2 - R4 - BSD