Hi! On Sun, 2022-12-18 at 16:03:01 +0100, Axel Beckert wrote: > Package: dpkg-dev > Version: 1.21.12 > Severity: wishlist
> for me it seems "obvious" that the way, in which build profiles are set, > is documented in dpkg-buildflags(1). But it isn't. It's only mentioned > dpkg-checkbuilddeps(1) and dpkg-buildpackage(1). Right (the only ones that end up making direct use of it). > It would be nice, if dpkg-buildflags(1) would at least contain a pointer > to where documentation about build profiles can found. And maybe also > why they aren't build _flags_ despite some of them, e.g. "noopt" and > "nocheck", look similar on a first glance. There's no noopt build profile though. :) I was about to ask where the confusion might be stemming from, but I guess it is precisely what you spelled it here, that "nocheck" is both a build profile and a build option? (For ref: https://wiki.debian.org/BuildProfileSpec#Map_DEB_BUILD_OPTIONS_to_namespaces, and also note in the definition where it mentions that both need to be set.) In principle I'd tend to avoid mentioning things that are unrelated to the specific tool, or even things that are "vendor policy" and not directly used by dpkg (such as most of the currently defined build profiles in Debian) in contrast to the mechanisms. But I guess I could add perhaps a generic text saying more or less: Some build profiles might require their counterpart to also be included in the build options, as they are currently not properly integrated, the list of such build profiles is vendor specific. or something along those lines. I think in the past there's been talk about making for example dpkg-buildpackage setting one if the other is set, but there was some resistance(?). At a guess, perhaps the fact that dpkg-buildpackage is not our official entry point, or perhaps giving freedom to users to specify one but not the other? But right now I do not exactly recall the details and would need to dig them up. Thanks, Guillem
