On Wed, Mar 04, 2020 at 04:37:47PM +0000, Dimitri John Ledkov wrote: > And if a saner/shorter version number is not possible, maybe Debian > does not deserve to ship acorn at all.
*Many* have complained about the version string, but nobody has come up with a saner way to * track what is bundled inside a source package * the versions of those things * automatically look up whether there are updates to any of those things when the bundled bits come from different sources, with different release schedules, etc. Note that uscan's integration into much of the Debian infrastructure is relevant here. A new approach _could_ be this, that I have yet to evaluate though: https://salsa.debian.org/debian/devscripts/-/merge_requests/156 The current version string is totally horrible and might be hard on humans, but otherwise accomplishes the above. If something you use is broken by it, please mention what it is. BTW, this bit of the OP: > It's not useful from a dependency point-of-view, > because a dependent package cannot specify a dependency on only the > component they care about, so they would have to include the versions of > the packages they don't care about too. it's not true: versioned provides are in place, and indeed nobody should depend on "node-debbundle-acorn". -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
