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
