easy way to fix broken packages?

flokno · Posted: Mon Feb 10, 2003 1:47 am Post subject: easy way to fix broken packages?

hello

is there an easy way to fix all broken packages caused by
- upgraded progs like kde 3 -> 3.1
(some progs compiled earlier depend on kde3's libaries)
- upgraded libs due to security reasons
- packages that depend on changed/updated packages higher in the decendancy tree?

maybe this feature should be planned for future portage versions.

any information would help me!

-- flo
ps: hope this is no dupe

David_Escott · l33t Joined: 12 Jan 2003 Posts: 952 Location: Boston, MA

reverse dependency checking is being implemented but for most applications this isnt necessary unless you unmerge the old versions. portage allows slots which will allow multiple versions of the same program to coexist. This way programs can link to old versions of libraries if they need to, however if the api hasnt changed then they can just link to the new ones without trouble.

flokno · Posted: Mon Feb 10, 2003 5:24 pm Post subject:

and what about old libs when i reemerge dependant packages. will they be cleaned, when they arn't needed anymore?
(=nothing depends on the old version?)

David_Escott · l33t Joined: 12 Jan 2003 Posts: 952 Location: Boston, MA

I think this falls under depclean but you may want to do this manually checking with qpkg to see that nothing is being used. This is a little beyond my knowledge of portage however so....

depclean
Cleans the system by removing packages that are not associated
with explicitly merged packages. Depclean works by creating the
full dependancy tree from the system list and the world file,
then comparing it to installed packages. Packages installed, but
not associated with an explicit merge are listed as candidates
for unmerging. WARNING: This can seriously affect your system by
removing packages that may have been linked against, but due to
changes in USE flags may no longer be part of the dep tree. Use
caution when employing this feature.