On Fri, Jul 1, 2016 at 3:58 PM, Tomas Orsava <torsava(a)redhat.com> wrote:
Oh, sorry, I didn't look at the user name :)
Could you please expand on what you have written here?
I'm not sure I follow you entirely.
So, the "problem" with --majorver-provides occurs when either of the
two conditions are true:
* There's no dependency on a specific version of the Python ABI
("python(abi) = X.Y") in the modules
* There's more than one package providing a python implementation per
major version. (i.e. a package providing "python(abi) = 3.4" and
"python(abi) = 3.5")
In either case, you wind up in a scenario where it's possible to BR a
module that would be mismatched to the Python implementation. That is,
the module would be installed in a path that doesn't match the Python
implementation. Thus, the package would be effectively broken, since
it won't work.
However, in Mageia (which is where a variant of this dependency
generator is already used), we've never had this problem because
there's a dependency that forces it to match to the proper Python
implementation (Requires on "python(abi) = X.Y").
And this generator has an additional protection (that doesn't exist in
the Mageia one) in that generated requires use
"pythonX.Ydist(CANONICAL_NAME)" no matter what.
As for the interpreter running the dependency generator, it defaults
to whatever /usr/bin/python is, unless you override it.
真実はいつも一つ！/ Always, there's only one truth!