Bug#73620: Policy example about INSTALL is wrong
On Tue, Oct 03, 2000 at 04:30:47PM -0700, Yves Arrouye wrote:
> Package: debian-policy
> Version: 3.2.1.0
>
> Section 4.1 of the policy manual says to build after setting
>
> INSTALL = install
>
> In addition to the fact that the example should use INSTALL_PROGRAM because
> of the strip example later in this section, the value of the variable should
> be /usr/bin/install. If it is set to a non-absolute path, configure will add
> dots in subdirectories to refer to the top-level command, and then calls to
> $(INSTALL) or $(INSTALL_PROGRAM) will fail, as in:
>
> ../install: No such file or directory
NB mentioning /usr/bin/install in Policy would be good also because some
lame configure scripts may not be using it, instead they'll be using the
supplied install-sh script. That's compatible with every Unix-like system
in the universe, but is also much much slower than /usr/bin/install.
--
Digital Electronic Being Intended for Assassination and Nullification
Reply to: