From owner-freebsd-hackers  Tue Apr  4 21:07:31 1995
Return-Path: hackers-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA02002 for hackers-outgoing; Tue, 4 Apr 1995 21:07:31 -0700
Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA01990 for <freebsd-hackers@freebsd.org>; Tue, 4 Apr 1995 21:07:27 -0700
Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.8/8.6.6) id UAA09498; Tue, 4 Apr 1995 20:06:46 -0700
From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com>
Message-Id: <199504050306.UAA09498@gndrsh.aac.dev.com>
Subject: Re: new install(1) utility
To: julian@tfs.com (Julian Elischer)
Date: Tue, 4 Apr 1995 20:06:46 -0700 (PDT)
Cc: freebsd-hackers@FreeBSD.org
In-Reply-To: <m0rwJuZ-0003w0C@TFS.COM> from "Julian Elischer" at Apr 4, 95 06:29:35 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 1904      
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

[CC: trimmed]
> 
> > 
> > > > > And jamming make-like dependency capability into install is a
> > > > > cockamamy way to fix it.
> > > > 
> > > > It has nothing to do with make-like dependency capabilities.  With the
> > > > addition of that option, install now determines if it really needs to
> > > > install the files rather than blindly doing it no matter what.
> > > 
> > > I think Terry means this:
> > > 
> > > ${DESTDIR}${BINDIR}${PROG}: ${.OBJDIR}/${PROG}
> > > 	install ${COPY} ${STRIP} -m ${BINMODE} -o ${BINOWN} -g ${GINGRP} \
> > > 		${PROG} ${DESTDIR}${BINDIR}
> > > 
> > > install:	${DESTDIR}${BINDIR}${PROG}
> > 
> > Ahh, but what if ${DESTDIR}${BINDIR}${PROG} was older than
> > ${.OBJDIR}/${PROG} simply because it was deleted during a purge of
> > /usr/obj. My arguement is that it doesn't *need* to be installed
> > (especially in the case of libraries).
> This is hte best argument I've heard for BOTH options..
> i.e. the dependencies under Make, AND the install that doesn't (sometimes)

Hey, two more people in agreement.  Or at least partly.  I am not
so sure about having install do the cmp, I think that part is best
left externally.  My reasoning here is that if the cmp is inside
install we will exec both install and cmp no mater what, if we do a
cmp || install
it would be possible to save the exec of install if the cmp successeds.

Using cksum is *not* the way to go, we already have Pouls benchmarks
of cmp vs cksum on this, and cksum is not fail safe, it is possible
for 2 files to have the same checksum but contain different data,
very unlikely, but possible.

I do see the need to have install have the -t option to copy time stamps.
Bruce, would this mean we could drop the ranlib after installing libraries?


-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                   Custom computers for FreeBSD