[Mageia-dev] Backports Summary
boklm at mars-attacks.org
Wed Jun 27 20:00:47 CEST 2012
On Wed, 27 Jun 2012, andre999 wrote:
>>> In your example, cauldron would probably require the libsomething.so.2, so
>>> if the backport requires could be adjusted to work with libsomething.so.1,
>>> we would keep the requires compatible with libsomething.so.2. If that
>>> isn't possible, then it wouldn't be accepted.
>> We cannot link a program with both libsomething.so.1 and
> If the spec file requires cannot be adjusted to accept linking with
> whichever of the 2 is available, then in that case the backport wouldn't be
> accepted - if my suggested restriction is accepted.
It's not adjusted in the spec file, it's built against the version that
is available in the repository when building the package, and require is
>>> I'm no expert of course, but it seems to me that it would be generally
>>> possible as long as there weren't important code changes made to make the
>>> backport work.
>>> So it would largely be a question of appropriately adjusting the specified
>> A lot of requires are generated automatically, we cannot change them
>> (and changing them would probably be wrong). And a lot of requires are
>> not versionned, but implicitly require the version available in the
>> same mageia release, without any guaranty that it works with a different
> You mean generated automatically in the spec file ? Surprising.
Generated by rpm find-requires scripts.
But discussing this if you don't know the basic functionning of rpm is a
waste of time, so end of discussion for me.
More information about the Mageia-dev