hello, On 8.3.2017 19:00, Todd Rme wrote:
There are some things that I feel are still ambiguous here:
thanks for the suggestions. I'm updating the wiki with answers.
1. Does the renaming in, for example, Requires, only rename packages that begin with "python-" or does it rename packages with "python-" appearing anywhere? So would "Require: foo-python-bar" be renamed?
No. Do you think it should?
What about with more complex expressions, such as "packageand(python-foo:%{bar})"?
I wrote packageand() support yesterday, after toying with your python-gobject package :) I completely forgot that this existed. The intention is to rename "package names starting with python-" (or "$flavor-"), so this should leave out "foo-python-bar" but should affect expressions that include python names. Once we adopt Fedora's pythonX.Ydist(), this will also be supported. I am only aware of packageand(), are there similar expressions that should be supported?
2. What about "Supplements"? Are python packages in that tag renamed automatically?
yes, as of yesterday :)
3. What if we need to BuildRequires the entire python interpreter, rather than python-base or python-devel? Would we just "BuildRequires: python" and "BuildRequires: python3", or is there a macro to handle that? If there is no macro, is "BuildRequires: python" or "BuildRequires: python2" preferable? What if we need to Requires the entire python interpreter?
There is no BuildRequires macro support for this. I'm considering creating a "python-full-stdlib" symbol which you would then put into %python_module, but that doesn't exist yet. BuildRequiring "python" should be exceptional, so I'm OK with listing the pythons manually. "python2" is the preferred name. (but as of right now I'm unsure whether it works in Leap < 42.3 -- it depends on whether they get the python update that is now headed to SLE) "Requires: python" works fine and gets renamed to the appropriate interpreter. regards m.