On Mon, Apr 04, 2022 at 08:17:03PM +0900, Olaf Meeuwissen wrote:
> Hi,
>
> Mark Hindley <mark@???> writes:
>
> > I have just built src:dummy-systemd-dev for experimental.
> >
> > The binary contains a single file[1] extracted from Debian's systemd binary
> > package. The file enables other package builds to query installation paths using
> > pkg-config(1).
> >
> > Whilst I have not tested all of the Build-Depends: systemd sources in our
> > archive, manual installation of dummy-systemd-dev has enabled compilation of
> > alsa-utils and pipewire. Further testing is welcome. There may still be packages
> > for which this is insufficient.
>
> Based on the thread content, I get the distinct impression that that
> Build-Depends: is really a "Build-Configure-Depends:" where the project
> uses autoconf, CMake or similar with a bit of code to check for the
> presence of systemd related header files and/or libraries. If so, I
> would sort of expect those projects to do the Right Thing and disable
> anything that really depends on systemd or fail to configure.
>
> If it doesn't do either of those and bombs partway through the build,
> that'd be a bug, in my dictionary.
>
> Assuming it does, any Debian "systemd-dev" kind of package should, for
> Devuan purposes, *not* include header files and/or libraries. It should
> only contain the bare minimum to let projects pass its configure stage,
> note the fact that there is no systemd support and do the Right Thing.

Could it be that it need the systemd dependency only if it is present? So on Devian you need the dependency but on Devuan you don't?