On Thu, Sep 08, 2011 at 03:38:39PM +0200, Raphael Hertzog wrote: > And still, this is a Makefile so you can quickly reuse Makefile snippets > that others have been writing to add support for supplementary targets > (like get-orig-source) or even to influence the environment (like the > Makefile snippets that dpkg 1.16.1 is going to provide). I have gone on record as saying that I don't think makefile includes are a suitable interface to use for common packaging infrastructure, because there are no limits on the effects they can have on the caller. Even when a stated interface declares such a limit, the developers are operating without a safety net in terms of the implementation, leaving a lot of room for bugs. For this reason, I would greatly prefer to not see makefile snippets provided by dpkg *at all*; and I don't find that this argument carries any weight with me as regards the question of requiring debian/rules to be a makefile or not. I do think that there are lots of other reasons we want to be able to rely on makefile behavior from debian/rules on the developer side - introspection for the build-arch transition being a good example of this. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slangasek@ubuntu.com vorlon@debian.org
Attachment:
signature.asc
Description: Digital signature