Bug#728200: debian-policy: force build tools to ensure source trees are build-ready
On Tue, Oct 29, 2013 at 12:41:45PM +0000, Ximin Luo wrote:
> Package: debian-policy
> Severity: important
>
> I was recently hit by this bug [1] which stems from inconsistent assumptions
> that various build tools have about the state of the build tree. I filed [2]
> to devscripts to suggest a fix.
I agree that debclean should be fixed, but your use of question marks suggests
that you are seriously confused about the policy.
The reason of bugs in devscripts is due to the introduction of the new source
format rather than misunderstanding the policy.
> However, policy wording could be better in this area, and it is especially not
> helpful for Section 4.14 [3] to effectively give free reign to the maintainer
> to make arbitrary instructions on how to take the source tree from an unpacked
> state to a build-ready state. (How does this even work with buildd??? Did you
> guys solve NLP???)
You are misreading 4.14 [3]. README.source documents how to edit the source
package and how to use new upstream tarball.
> I would suggest policy make explicit definitions for the terms "unpacked" state
> vs "build-ready" state, and force build tools to detect and reject performing
> `debian/rules` actions on source trees that are not "build-ready". It just
> doesn't make sense for this to happen, no good result can come out of it.
As far as policy is concerned, freshly unpacked source package are build ready.
> Or probably better, the build-tool can simply make the source tree build-ready
> by running `dpkg-source --before-build` or `debian/rules patch` before running
> other debian/rules actions. (This also requires "patch" to be idempotent.)
'debian/rules patch' is deprecated by the new source format "3.0 (quilt)"
Cheers,
--
Bill. <ballombe@debian.org>
Imagine a large red swirl here.
Reply to: