Re: Bug#1093222: Minimizing build-arch for pam

[Sam Hartman <hartmans@debian.org>]

>>>>> "Simon" == Simon McVittie <smcv@debian.org> writes:

    Simon> On Thu, 16 Jan 2025 at 09:38:38 -0700, Sam Hartman wrote:
    >> But the meson setup call is in override_dh_auto_configure.  I
    >> don't know at that point how to figure out of I am building arch
    >> all packages.

    Simon> I find that it's often better to do this in terms of "am I
    Simon> building package X?" instead of "am I building arch: all
    Simon> packages?" because that way, you will also get the correct
    Simon> answer when dealing with build-profiles.

    Simon> We do this a lot in GNOME and GNOME-adjacent
    Simon> packages. Something like this (in this case taken from
    Simon> gobject-introspection, and enabling/disabling the gtk_doc
    Simon> option depending on whether we are building the -doc
    Simon> package):

    Simon> built_binaries := $(shell dh_listpackages)

Okay, so dh_listpackages is smart enough to know what kind of build it
is in even when called from override_dh_auto_configure?
I didn't know that, and yes it makes this easy.

I also had somehow missed the Build-Profiles binary package control
field.
To confirm, it would be reasonable to mark libpam-doc with

Build-Profiles:  <!nodoc>