harmful python-* Provides without epoch

Jakub Bogusz qboosh at pld-linux.org
Sat Dec 11 17:59:26 CET 2004


On Sat, Dec 11, 2004 at 05:35:21PM +0100, Paweł Sakowski wrote:
> On Sat, 2004-12-11 at 17:24 +0100, Jakub Bogusz wrote:
> > Some workaround could be not to use epoch in less-than rules... but it
> > could turn out harmful in the future.
> > 
> > Does anyone have better, reliable solution than dropping these
> > non-epoched provides and updating existing non-epoched dependencies?
> 
> Provides: python(something) = %{py_ver}
> and modify pyrequires_eq to require the virtual capability, without an
> epoch.

Hm... maybe just
Provides: python(ver) = %{py_ver}
in python-libs?

The rest of dependencies don't need to be so strict.
python-libs version determine byte-compiled object format and
/usr/*/python* dir names.
The rest of dependencies could be just >=.

In fact, python-libs deps could be generated automagically using
`find -name '*.py[co]' | xargs file` and parsing strings like:
/usr/lib/python2.3/site-packages/libxml2.pyo: python 2.3 byte-compiled

The rest of python- deps can be used manually without version on
with just >= rule (so there is no need for %pyrequires_eq macro).
(until some good python dependency generator comes)


-- 
Jakub Bogusz    http://cyber.cs.net.pl/~qboosh/




More information about the pld-devel-en mailing list