Date: Tue, 4 Apr 1995 15:38:27 -0700 (PDT) From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> To: terry@cs.weber.edu (Terry Lambert) Cc: nate@trout.sri.MT.net, kargl@troutmask.apl.washington.edu, freebsd-hackers@freefall.cdrom.com Subject: Re: new install(1) utility Message-ID: <199504042238.PAA08762@gndrsh.aac.dev.com> In-Reply-To: <9504042306.AA21122@cs.weber.edu> from "Terry Lambert" at Apr 4, 95 05:06:07 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > > You happened to have picked a bad example. There are include files > > that this holds true for, and that is due not really having good > > support in the *.mk files for a includes: rule. I would rather > > see the above type of thing folded into the .mk files and not > > muck with the install binary. > > Exactly; it's an issue of not doing the wrong thing because you > have a dependency which stops you before you screw up. > > > > 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} > > Much cleaner than what I was thinking! Thank you! Okay, I'll play with this a little and see if technically this can be made to work. I will not have the time to do a full implementation though. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504042238.PAA08762>