QUESTION

Is there a
 - safe
 - efficient
way to clean up '/usr/lib'?

Low priority.  If somebody has a good idea and has nothing better to do ...

DETAILS

As a somewhat extreme example, my library has ended up with stuff of this
kind:

[]% ls -ogtr libgdk-x11-2.0.so* | cut -c13-

 1453058 2005-10-09 12:44 libgdk-x11-2.0.so.0.600.7
 1483071 2007-03-01 22:53 libgdk-x11-2.0.so.0.800.20
 1813487 2008-06-24 23:07 libgdk-x11-2.0.so.0.1200.10
 1887699 2009-06-27 11:20 libgdk-x11-2.0.so.0.1400.7
 2155925 2010-06-27 20:49 libgdk-x11-2.0.so.0.2100.0
 2184669 2010-06-27 21:19 libgdk-x11-2.0.so.0.2102.0
 2148459 2011-03-04 00:51 libgdk-x11-2.0.so.0.2400.0
 2148463 2011-03-09 19:21 libgdk-x11-2.0.so.0.2400.1
 2148403 2011-03-28 17:56 libgdk-x11-2.0.so.0.2400.3
 2148527 2011-07-14 20:15 libgdk-x11-2.0.so.0.2400.5
 2486893 2012-01-09 14:12 libgdk-x11-2.0.so.0.2400.8
 2487926 2012-03-19 22:57 libgdk-x11-2.0.so.0.2400.10
 2764338 2012-12-01 17:50 libgdk-x11-2.0.so.0.2400.13
 2765279 2013-04-29 13:30 libgdk-x11-2.0.so.0.2400.17
 2768025 2013-10-04 12:59 libgdk-x11-2.0.so.0.2400.21
      27 2013-10-04 12:59 libgdk-x11-2.0.so.0 -> libgdk-x11-2.0.so.0.2400.21
      27 2013-10-04 12:59 libgdk-x11-2.0.so   -> libgdk-x11-2.0.so.0.2400.21

Not pretty.  Apparently, a sizable dead space waiting to be reclaimed.

------

Now for a practical example of an ill-advised clean-up attempt.
Say, I see something like

[]% ls -ogtr libjpeg.so* | cut -c13-

 137053 2005-10-01 13:12 libjpeg.so.62.0.0
     17 2009-06-25 19:09 libjpeg.so.62 -> libjpeg.so.62.0.0
 772984 2010-01-01 15:52 libjpeg.so.7.0.0
     16 2010-01-01 15:52 libjpeg.so.7 -> libjpeg.so.7.0.0
 921939 2012-03-27 12:51 libjpeg.so.8.4.0
 425541 2013-09-30 12:05 libjpeg.so.8.0.2
     16 2013-09-30 12:05 libjpeg.so.8 -> libjpeg.so.8.4.0
     16 2013-09-30 12:05 libjpeg.so -> libjpeg.so.8.0.2

'libjpeg.so.7.0.0' (along with 'libjpeg.so.62') would look like an easy kill
to my untrained eye:

[]% rm -f libjpeg.so.7*

NOT so fast.

[]% gimp
 GEGL-geglmodule.c-Message:
  Module '/usr/lib/gegl-0.2/jp2-load.so' load error:
   libjpeg.so.7: cannot open shared object file: No such file or directory

Oops!
On closer inspection,

[]% ldd /usr/lib/gegl-0.2/jp2-load.so
        ...
        libjpeg.so.7 => not found               [!!!!!!]

i.e., some crazy, hidden dependency of a dependency lying in wait for the
amateur!

Thanks,
-- Alex

PS  If people are worried my system has been thrown in disarray, everybody
calm down.  Instead of deleting libjpeg.so.7* as "simulated" above,
what I actually did was

[]% mv libjpeg.so.7 libjpeg.so.7.bak
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to