• build-dependencies metapackages

    From =?UTF-8?Q?Julien_Plissonneau_Duqu=C@21:1/5 to All on Wed Jan 8 10:00:02 2025
    Hi,

    Working on libjackson2-* upgrades on the side I'm experimenting
    introducing a build-dependencies metapackage [1] to avoid repeating them
    all in every package that build-depends on libjackson2-core-java.

    It works so far, but I'm not completely sure it's an appropriate way to
    deal with the issue. Among the advantages, any update of jackson-core
    (that ships the parent POMs used by other jackson-* builds) changing the
    set of build-dependencies will be automatically pulled by the other
    packages without needing to update them individually, and that may help
    prevent future build failures. Among the possible issues, these build
    deps are now transitive, and some tooling may miss the need to rebuild
    and retest the package after one of these b-d is updated but not
    jackson-core itself.

    WDYT?

    Cheers,


    [1]: https://salsa.debian.org/jpd/jackson-core/-/blob/981930044f8e4097d866c6837cd8c8b8b45ecc54/debian/control#L62-L94

    --
    Julien Plissonneau Duquène

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Julien_Plissonneau_Duqu=C@21:1/5 to All on Thu Jan 9 17:50:01 2025
    Le 2025-01-08 09:49, Julien Plissonneau Duquène a écrit :
    I'm experimenting introducing a build-dependencies metapackage

    So far I was told on IRC that
    the package should be libjackson2-java-dev I guess
    which looks better than the current name so I'm going to change the
    metapackage name to libjackson2-core-java-dev

    and also that:
    one price you'll pay is that autopkgtests are not scheduled for
    transitive reverse build-depends, only for direct reverse (build-)
    depends.
    which conflicts with my goal of getting more autopkgtests especially
    with build tools and dependencies.

    Right now I'm leaning more towards keeping the metapackages and
    contributing later to autopkgtests to automatically add the dependencies
    of the metapackage to the set of packages that triggers tests.

    One last thing, I noticed this old RFP [1] for the parent POMs that are
    now shipped with libjackson2-core-java. Asking just in case, is there a possible use case for shipping there separately?

    Cheers,


    [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760834
    --
    Julien Plissonneau Duquène

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)