[repo-coord] Re: Packaging Dilemma

[Axel Thimm]

For PyVault (packages for latest python version) I would suggest:

o package the latest python into /usr/bin/python%{pyver} into
  python%{pyver}-...rpm. Many pythonXX-...rpm packages will be able to
  coexist (for transition/migration purposes of PyVault hwen the next
  python release emerges).
o package one "wrapper" package "python" (and "python-devel")
  requiring the lastest from the above and symlinking /usr/bin/python
  to /usr/bin/python%{pyver} (similar for /usr/bin/python2). E.g. the
  python package is just a "pointer package".
o build all the rest simply against "python-devel"
  package, but use non-versioned BuildRequires: python [>= ...]
  dependencies

This should resolve most of the problems, and provide specfiles that
would look very clean and would require no rewrites for moving on to
the next python version.

You could still place the python version into the rpm name of the
modules to allow concurrent installation of the same python modules
for different python abis (just like kernel module rpms), but I
understand that this is not the purpose of PyVault, so simply head for
building for the latest available python (which is probably offered by
PyVault as well).

Does that make any sense?
-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/repo-coord/attachments/20040525/03281d8d/attachment.bin