Starting from a 1.5.2 system, i've upgraded to -current. So far, so
good.

But i've noticed that a 'ls -lt' in /usr/lib show me a lot of 'old'
 shared libs and links to them (the problem doesn't appear in /bin,
 /sbin, /usr/sbin /usr/libexec and /usr/bin as new versions of the
 programs has the same names of previous one, hence overwriting
 them). And i don't like obsolete files on my system...

If i make build today, Sep 30, could i delete the older libs in
/usr/lib (i never put anything in this directory and i guess that
packages don't either...).

Example:

/-----------------
| $ ls -lt libroken*
| lrwxr-xr-x  1 root wheel     16 Sep 30 19:29 libroken.so -> libroken.so.12.2
| lrwxr-xr-x  1 root wheel     16 Sep 30 19:29 libroken.so.12 -> libroken.so.12.2
| -r--r--r--  1 root wheel  48918 Sep 30 19:29 libroken.so.12.2
| -r--r--r--  1 root wheel  85198 Sep 30 19:29 libroken_pic.a
| -r--r--r--  1 root wheel  88794 Sep 30 19:29 libroken_p.a
| -r--r--r--  1 root wheel  80836 Sep 30 19:29 libroken.a
| lrwxr-xr-x  1 root wheel     16 Sep 14 00:08 libroken.so.11 -> libroken.so.11.0
| -r--r--r--  1 root wheel  43554 Sep 14 00:04 libroken.so.11.0
| -r--r--r--  1 root wheel  43270 Jul 25 23:13 libroken.so.12.1
\-----------------

Could i delete libroken.so.11, libroken.so.11.0, libroken.so.12.1 ?

I suppose that only libs built with my last 'make build' are up to
date but i prefer take some advices before doing unwanted deletions...

I know i cannot apply this reasoning to /usr/include as include files
are simply copied, not built: their dates are those of
/usr/src/include (BTW, i think it will be better to enforce the copy
date to these files, too, for the same reasons, but that not the place
to talk about that)

   Thanks in advance,
-- 
Éric Jacoboni, né il y a 1305333748 secondes