Re: Can we stop revbumping the world please?

[Thomas Klausner <wiz%NetBSD.org@localhost>]

Hi,

there seems to be confusion about the need for the revbumps, so even
though this is an old topic and I thought it was well understood, let
me try explaining again.

icu provides some libraries. Their major versions change with every
version bump of the package, so when updating icu from 75.x to 76.x,
libfoo.so.75 becomes libfoo.so.76.

So if you just replace icu in place, all your packages linking against
icu will stop working because they look for the now-removed
libfoo.so.75.

The binary packages of icu 75 and 76 are thus incompatible.

The other way around, if you build a binary package now from scratch,
you'll get a version linked against libfoo.so.76.  If you publish this
version in a binary package repository, and someone installs this
package, pkg_add of the package will fail because they might still
have icu 75 installed but the binary package now needs 76.

So we need to mark packages as both:
- requiring icu 76 if built against icu 76
- having a different file name when built against 75 vs. 76

This is what the recursive bumps do.

- ABI depends are bumped, so when building packages from source, the
  new icu will be required

- the recursiveness makes sure this also applies if icu is just an
  indirect dependency (i.e. libbar uses icu, then all users of libbar
  also need the bump)

- the PKGREVISION bump makes sure you can differentiate between a
  foobar binary package built against icu 75 (before the version bump)
  and one built against icu 76 (after the version bump).

So no, the bumps are required and we can't get rid of them, sorry.
 Thomas