I would like to fix %python-provide.

See https://bugzilla.redhat.com/show_bug.cgi?id=1351136

I mentioned PIL case there as well.

-Igor Gnatenko


On Jul 2, 2016 11:27 AM, "Sandro Mani" <manisandro@gmail.com> wrote:
Hi

I'm looking at modernizing the python-pillow spec and have a question about %python_provide: The python{2,3}-pillow also provide the legacy python{,2,3}-imaging names, how should this be handled with %python_provide? I.e.

%package -n python2-pillow
%{?python_provide:%python_provide python2-imaging}

will currently result in

python-imaging = 3.3.0-1.fc25
python-imaging(x86-64) = 3.3.0-1.fc25

and

%package -n python3-pillow
%{?python_provide:%python_provide python3-imaging}

won't generate any python-imaging provides at all.

This makes sense from my understanding of %python_provide, however I suspect that the only way to handle the provides for the legacy name is to hard-code them to

%package -n python2-pillow
Provides: python-imaging = %{version}-%{release}
Provides: python2-imaging = %{version}-%{release}

%package -n python3-pillow
Provides: python3-imaging = %{version}-%{release}

And manually switch move the Provides: python-imaging to python3-pillow when the default interpreter changes.

Is this correct?

Thanks

Sandro


--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org