From owner-freebsd-hackers  Tue Apr  4 18:30:36 1995
Return-Path: hackers-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA28656 for hackers-outgoing; Tue, 4 Apr 1995 18:30:36 -0700
Received: from tfs.com (mailhub.tfs.com [140.145.250.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id SAA28650 for <freebsd-hackers@freefall.cdrom.com>; Tue, 4 Apr 1995 18:30:34 -0700
Received: by tfs.com (smail3.1.28.1) 
Message-Id: <m0rwJuZ-0003w0C@TFS.COM>
From: julian@tfs.com (Julian Elischer)
Subject: Re: new install(1) utility
To: nate@trout.sri.MT.net (Nate Williams)
Date: Tue, 4 Apr 1995 18:29:35 -0700 (PDT)
Cc: rgrimes@gndrsh.aac.dev.com, terry@cs.weber.edu,
        freebsd-hackers@freefall.cdrom.com
In-Reply-To: <199504042329.RAA08021@trout.sri.MT.net> from "Nate Williams" at Apr 4, 95 05:29:41 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 957       
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

> 
> > > > 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)

> 
>