>>"Yves" == Yves Arrouye <[EMAIL PROTECTED]> writes:
Yves> Section 4.1 of the policy manual says to build after setting
The policy also explicitly states it is a mere example, and
does not, by any means decree that usage.
Yves> INSTALL = install
Yves> In addition to the fact that the example should use
Yves> INSTALL_PROGRAM because of the strip example later in this
Huh? What is INSTALL_PROGRAM?
__> zgrep -i install_p /usr/local/src/Packages/debian-policy/policy.text.gz
__>
Yves> section, the value of the variable should be
Yves> /usr/bin/install.
I prefer to not have full path names set in rules file (as an
extention of the rationale for not having them in maintainer
files). Not having full path names allows me to set the path to a non
standard one while testing builds.
Yves> If it is set to a non-absolute path,
Yves> configure will add dots in subdirectories to refer to the
Yves> top-level command, and then calls to $(INSTALL) or
Yves> $(INSTALL_PROGRAM) will fail, as in:
Sounds like a bug in configure.
If you _must_ use a broken configure system, you can set the
full path four your local rules file. It should certainly not be
embedded in policy.
manoj
--
The better the state is established, the fainter is humanity. To make
the individual uncomfortable, that is my task. Nietzsche
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
