Bug#88029: allow rules file to be non-makefile
On Thu, Mar 01, 2001 at 11:57:50AM +1000, Anthony Towns wrote:
> > This file must be an architecture-independent non-interactive executable
> > which has to take the following parameters on the command line and act
> > accordingly:
>
> Or we could go back to how the packaging manual says it:
>
> This file is usually an executable makefile, and contains packages
> specific recipes for compiling the package and building binary
> package(s) out of the source.
s/packages\nspecific/package-specific/
> The only RC part of this is ensuring the package builds in the normal
> fashion, and if it doesn't, well, that's already considered RC anyway.
Right. This would do, I guess.
> > The second paragraph about the shebang should be removed. I think it's safe
> > to assume that you'd make an executable file actually runnable... Then
> > again, I'm not sure, maybe this does have to be spelled out since it's in
> > Policy.
>
> The reason it's spelt out is in case people don't think of using a #! for
> a makefile; it's not really all that common a thing to do.
Yes but
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.
is quite make-specific, and it includes a "must". This would have to be
reworded.
What does the old packaging manual say here, is it different?
> Policy's not just a set of dictata that others must obey; it's guidelines
> on how to make high quality packages.
Um, okay, tell me something new. :)
--
Digital Electronic Being Intended for Assassination and Nullification
Reply to: