Re: /lib symlinks problem?

Sheldon Hearn wrote:
> On (2003/09/02 09:43), Ian Freislich wrote:
> 
> > > I posted one approach to this today... touch a file right before you
> > > start installworld, then consider anything not newer than that file a
> > > candidate for disposal. There is currently something weird going on in
> > > /usr/lib though... a lot of the files don't have newer dates, I haven't
> > > tracked down why yet.
> > 
> > That's because bsd.lib.mk and bsd.own.mk hardcode '-C' for install.
> 
> Which a few of us have complained about and subsequently settled on
> local patches for. :-(

Which is what I eventually did too after nearly destroying half of
/usr/lib because /usr/src/share/examples/etc/make.conf and make.conf(5)
*LIE* about (or at the very least misrepresent) what really happens.
The explanation 'these files are dependencies' doesn't really explain
the need for install -C to me and just makes it harder to find what
was installed and what was stale.

I propose the following patch to make.conf(5) and something similar
to make.conf:

Index: make.conf.5
===================================================================
RCS file: /home/ncvs/src/share/man/man5/make.conf.5,v
retrieving revision 1.78
diff -u -d -r1.78 make.conf.5
--- make.conf.5	29 Aug 2003 11:24:53 -0000	1.78
+++ make.conf.5	2 Sep 2003 08:11:10 -0000
_at__at_ -181,11 +181,15 _at__at_
 .It Va INSTALL
 .Pq Vt str
 the default install command.
-To have commands compared before doing
+To have targets compared with the source before doing
 the install, use
 .Bd -literal -offset indent
 INSTALL="install -C"
 .Ed
+Note that some system Makefile includes
+hardcode options for
+the supplied install command.
+Your mileage may vary.
 .It Va LOCAL_DIRS
 .Pq Vt str
 List any directories that should be entered when doing