On Mon, 31 Aug 2026 at 18:43, Bruno Haible <[email protected]> wrote: > > Luca Boccassi wrote: > > Yes, that's the mapping used for both rpm and deb packages, both of > > which have those 3 levels of dependency "strength" (mandatory -> > > optional installed by default -> optional not installed by default). > > The scripts and macros/tools to parse them and use them for package > > builds can be found on the following repo ... > > > > I think distros using formats other than deb/rpm (arch/nix) were > > looking into this at some point, but I'm not sure of the current > > status and what was implemented, if anything. > > Thanks for the confirmation and info. I'm adding documentation for > these priorities. > > The wording "core"/"important"/"secondary" functionality is taken from > the spec. > > I'm not taking the wording "the binary will work" from the spec, because > it has proven to be subject to interpretation. (Hopefully the terms > "core"/"important"/"secondary" are less subject to discussion.) > > The wording "This priority usually maps to ..." is a way to summarize > what your tools do. "usually" because a packager is free to not use the > tools or or may define the package dependencies as they like. > > Hope this doc is OK with you?
Looks great, thanks
