On Fri, 15 Dec 2023 16:42:34 +0000 Sean Whitton
<spwhit...@spwhitton.name> wrote:
Hello,
On Sat 02 Dec 2023 at 01:22am +01, Guillem Jover wrote:
> Starting with dpkg 1.22.0, it implements a dpkg-build-api mechanism
> similar in concept to the debhelper-compat levels.
>
> You can check its documentation in the dpkg-build-api(7) and
> dpkg-buildapi(1) manual pages.
>
> I think at least the part that involves the Rules-Requires-Root field
> which in level 1 defaults to value «no» instead of «binary-targets»
> should be documented in the Debian policy.
Agreed. Thanks for the report.
> I'm ambivalent on whether documenting the general mechanism in Debian
> policy makes sense though.
When many/most Debian package maintainers need to know about this, as
they do debhelper compat, then we should add it, but until then, perhaps
not.
--
Sean Whitton
Hi,
Can we have a trivial editorial change to the Rules-Requires-Root
paragraph saying that default depends on the `dpkg-build-api` used?
Bringing it up, because we are seeing a recommendation for people to add
a `Rules-Requires-Root: no` even though it is the default and redundant
because "policy and lintian said so".
Best regards,
Niels
PS: Concrete example I noticed was in #1078267, but I doubt it is a lone
case if we dig deeper.
