> "Rodney W. Grimes" wrote:
> > Good analysis deleted...
> > 
> > > src/usr.bin/xinstall could probably have been named src/usr.bin/install,
> > > but PROG has to be xinstall regardless.  I guess they kept the two as
> > > xinstall for consistancy and in case there were other gotcha's like this.
> > 
> > But you forgot what happens if you have a ``file'' named install:
> > 
> > cd /tmp
> > mkdir install
> > make install
> > 
> > Now you know the real reason the directory is called ``xinstall''.
> 
> Ahh yes, of course.  'cd src/usr.bin; make install'  would fail. :-)

Actually it use to silently do the wrong thing... nothing at all that is :-)

It doesn't anymore since the .mk system has a special internal target
that deals with the fact that src/usr.bin is simply a directory that has to
be iterated over:

Orbit.hpc1.com:root{101}# cd /usr/src/usr.bin
Orbit.hpc1.com:root{102}# mkdir install
Orbit.hpc1.com:root{103}# make install
===> apply
install -c -s -o root -g wheel -m 555   apply /usr/bin
install -c -o root -g wheel -m 444 apply.1.gz  /usr/share/man/man1
===> at
install -c -s -o root -g wheel -m 4555   at /usr/bin
...


-- 
Rod Grimes - KD7CAX @ CN85sl - (RWG25)               [EMAIL PROTECTED]


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

Reply via email to