Skip to content

d/control: Replace build-dependency on libgirepository1.0-dev

Simon McVittie requested to merge wip/no-libgirepository1.0-dev into debian/latest

  • d/control: Use ${gir:Depends} instead of hard-coding

    This avoids mistakes, and will make it easier to implement the <!nogir> build-profile at a later date, if desired.

  • d/control: Replace build-dependency on libgirepository1.0-dev

    libgirepository1.0-dev cannot be Multi-Arch: same and should be phased out during the trixie cycle.

    The versioned build-dependency on gobject-introspection is for the code-generation tools.

    The build-dependency on gir1.2-gio-2.0-dev and gir1.2-gobject-2.0-dev is because Gio-2.0 and GObject-2.0 are required during compilation: they are passed to g-ir-scanner via its --include option, as part of libmanette_gir_includes in src/meson.build. The virtual package names to depend on are mechanically derived from the name of the .gir file.

  • d/control: Explicitly build-depend on gir1.2-gudev-1.0-dev

    This is necessary because GUdev-1.0 is passed to g-ir-scanner via its --include option, as part of libmanette_gir_includes. Not all -dev packages provide this systematically-named virtual package yet, but gudev does.

    In practice GUdev-1.0.gir is part of libgudev-1.0-dev which we already build-depend on, but declaring the dependency explicitly will make it possible for gudev to implement the <!nogir> build-profile in future, if desired.

Normally I'd just upload this, but I'm opening it as a MR so that we have an example to point to when asking maintainers of other packages to stop using libgirepository1.0-dev.

Merge request reports