Sunday, October 01, 2023

OS version in packages

Every release, it's the same dance: a few packages want version bumps
because the OS version changed.

This means a bit of work for naddy, and noise for most of us: I tend to
have a bulk in-progress while this is going on, so my plist get bumped, and
then later I get to the new version, and I get a bunch of trivial errors
thanks to plist changes for packages that already got bumped (gratuitously)
for me.

But basically, this is useless: due to the way we do releases, OS version
doesn't mean ANYTHING with respect to those pieces of software.

I propose that, after 7.4, we get rid of those pesky version numbers that
are useless for us. We did that in base for perl (did we do it for base gcc
as well, I don't remember) and that infestation of locusts that was promised
still hasn't come.

I don't think software like octave or xemacs deserve special treatement.
Do they ?

No comments:

Post a Comment