On Sun, Sep 06, 2020 at 10:53:05PM +0200, Christian Kastner wrote: > It seems that "nocheck" and "nodoc" can be used with both variables. > > However, which one is to be used in debian/rules recipes? Or both, as > suggested here [1]?
The thing is, according to the build profile spec, if you specify nodoc
or nocheck in _PROFILES you *MUST* also specify it on _OPTIONS (talking
about when you do the build), so…
> Looking at random packages, newer packages seem to favor just checking
> DEB_BUILD_PROFILES to conditionally build documentation, but that would
> mean that DEB_BUILD_OPTIONS as recommended by policy is not honored.
Yeah, that might cause chances of failing builds if built with nodoc I
guess…
> Or do dpkg or debhelper apply some kind of mapping logic from _OPTIONS
> to _PROFILES for the popular options nocheck, nodoc, noopt?
debhelper does. various helpers do things differently with such
options. You should read the manpages for more details.
> Or are we supposed to transition to just _PROFILES in the long term?
There were talks around that with the people involved in writing up the
_PROFILES spec, not sure where that go (nowhere I think).
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
