Hi,
On Mon, Aug 28, 2000 at 05:59:11PM +0200, Josip Rodin wrote:
> Which is rather unwarranted... all that should be necessary is a executable
> file that can act differently based on the first command-line argument
> passed to it. Whether it is makefile, a shell or a Perl script, or even a
> compiled program (yuck :), it shouldn't matter.
Not entirely correct. I am not trying to split hairs here, but it is really
important that debian/rules is architecture independant, read: not in a
binary format, but a script. The packaging manually actually says it is a
makefile:
3.2.1. `debian/rules' - the main building script
------------------------------------------------
This file is an executable makefile, and contains the package-specific
recipies for compiling the package and building binary package(s) out
of the source.
It must start with the line #!/usr/bin/make -f', so that it can be
invoked by saying its name rather than invoking `make' explicitly.
I don't know if Manoj succeeded in making the packaging man a part of the
policy. And, I wouldn't mind if perl or shell scripts are allowed (or any
interpreter, which probably needs to be in Build-Depends then). They can
even compile a debian/rules2 program and use that for further processing.
Thanks,
Marcus
--
`Rhubarb is no Egyptian god.' Debian http://www.debian.org Check Key server
Marcus Brinkmann GNU http://www.gnu.org for public PGP Key
[EMAIL PROTECTED], [EMAIL PROTECTED] PGP Key ID 36E7CD09
http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ [EMAIL PROTECTED]
