[Pkg-javascript-devel] Bug#940708: Bug#940708: Bug#940708: acorn: please revisit your versioning strategy before making a sid upload
Pirate Praveen
praveen at onenetbeyond.org
Wed Mar 4 17:36:00 GMT 2020
On 2020, മാർച്ച് 4 10:40:30 PM IST, Mattia Rizzolo <mattia at debian.org> wrote:
>*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
That is not correct. Xavier (yadd) proposed 3 solutions already. Hope he will share the relevant proposals.
>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".
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
More information about the Pkg-javascript-devel
mailing list