[Rpm-maint] [rpm-software-management/rpm] Enhance requires with version information from the build root. (PR #2372)

[Gordon Messmer]

As far as I know, the blocking issue here is simply a decision about where to get the version of the library.  Among others, options include:

1: the rpm version of the package that owns the library.  Not a good solution because I think the maintainers don't want elfdeps to access the RPM DB during the build, and because it'd make interchangeable library implementations much harder.

2: a version string derived from the target of the symlink that ELF files refer to.  This requires *some* coordination for interchangeable libraries.  It also requires a two-phase rollout in which packages "provide" new capabilities and then later "require" those new capabilities.  And once that two-phase rollout is complete, old builds (which might be present in SUSE) can't be used any more.

3: a version string stored in a text file, defaulting to the version of the package that provides the library, but optionally defined by the packagers.  Requires no coordination upstream, and supports organic rollout.

4: the same version stored somewhere else.  Maybe in an extended attribute.  Do extended attributes work properly in environments like mock container builds?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2372#issuecomment-2035549671
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/pull/2372/c2035549671 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20240403/33e7fafa/attachment.html>