On 2002-11-23 10:36, Mark Murray <[EMAIL PROTECTED]> wrote:
> > Apparently editors/vim-lite had picked up an old, obsolete libposix*.so
> > from one of the past installations and linked against that.  Deleting
> > the port and reinstalling it worked like a charm, which made me think
> > a bit...  Should we recommend in UPDATING that source upgrades include
> > something similar?  Well, maybe not all the time (since ports can
> > break like vim did for me), but at least under a "making your /usr as
> > clean as possible" paragraph?
>
> I would support this, as long as it was not compulsory.

That's fair enough.  I wasn't implying that everyone should do this,
all the time.  How does the following footnote look?

%%%
Index: UPDATING
===================================================================
RCS file: /home/ncvs/src/UPDATING,v
retrieving revision 1.228
diff -u -r1.228 UPDATING
--- UPDATING    30 Oct 2002 20:11:07 -0000      1.228
+++ UPDATING    23 Nov 2002 17:03:07 -0000
@@ -1017,6 +1017,7 @@
                                                        [1]
        <reboot in single user>                         [3]
        mergemaster -p                                  [5]
+       <maybe clean up /usr/include and /usr/lib>      [10]
        make installworld
        mergemaster                                     [4]
        <reboot>
@@ -1116,6 +1117,25 @@
 
        [9] When checking out sources, you must include the -P flag to have
        cvs prune empty directories.
+
+       [10] Just before running "make installworld" in single user mode, you
+       might want to run the following to make sure there are no stale
+       include files or libraries in your installed system:
+               cd /usr
+               mv include include.old
+               mkdir include
+               mtree -deU < /usr/src/etc/mtree/BSD.include.dist
+               mv lib lib.old
+               mkdir lib
+               ldconfig -elf /usr/lib.old
+       Note that you should be careful when libraries have been obsoleted,
+       since it is possible for some of your ports or packages to break, if
+       they had been linked against libraries that are moved to /usr/lib.old
+       by this.  Don't remove /usr/lib.old right away!  You might find that
+       it still has libraries you need.  After you have installed everything
+       and checked that no problems of missing libraries exist, you can
+       safely remove both /usr/include.old and /usr/lib.old.
+
 FORMAT:
 
 This file contains a list, in reverse chronological order, of major
%%%

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to