Re: Can we stop revbumping the world please?

["Dr. Thomas Orgis" <thomas.orgis%uni-hamburg.de@localhost>]

Am Tue, 19 Nov 2024 04:22:32 +0000
schrieb David Holland <dholland-pkgtech%netbsd.org@localhost>:

> In the specific case of icu I noticed the other day that homebrew
> carries multiple versions, and obviously we'd rather not do that but
> maybe we should think about it.

Of course multiple versions are a path to avoid short-time hurt, for
more disaster later. For boost it might be just necessary to support
packages diverging in their needs/support for boost versions. But for
ICU, I am not aware of API issues, just that one needs to re-build
dependent stuff.

I understood that the underlying problem in pkgsrc architecture is that
indirect dependencies are resolved to be direct dependencies, each
build being marked as possibly directly linking to any library that a
dependency depends on. So, a new iteration of buildlinks that does
_not_ resolve indirect deps?

In Source mage, we either check the direct dependents of a package if
they need to be re-built for ABI changes or, at user discretion, offer
a way to check all installed packages if they are broken by an update —
and even then only re-building those that are missing libraries now
(so.(x-1)).

I am not sure how tricky it would be to (re-)introduce a notion of
direct and indirect dependencies in pkgsrc, and do re-builds only on
direct relations. For sure there are lots of packages now that do not
mention dependencies that they get by way of including a buildlink file
of another dependency. Lots of packaging cleanup ahead.

(And then perhaps the odd case of a dependency of a dependency actually
changing ABI of the direct dependency and so still requiring a rebuild
of the remote package.)


Alrighty then,

Thomas

-- 
Dr. Thomas Orgis
HPC @ Universität Hamburg