python2.2 -> python2.3

[Alan Milligan]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

| Warren Togami wrote:
|
|>> Alan Milligan wrote:
|>
|>>>> What we have here doesn't really qualify as bugs.  Our stuff falls
into
|>>>> two major components; (i) implementing the following macros:
|>>>>
|>>>> %pythonprefix /usr
|>>>> %__python %{pythonprefix}/bin/python
|>>>> %pythonversion %(python -c 'import sys;print(sys.version[0:3])')
|>>>> %pythonpath %{pythonprefix}/lib/python%{pythonversion}
|>>>> %pythoninclude %{pythonprefix}/include/python%{pythonversion}
|>
|>>
|>>
|>> Sorry, these changes are too invasive at this point, and even
|>> potentially wrong.  What about multilib?
|
|
| %pythondir %(python -c 'from distutils import sysconfig; print
sysconfig.get_python_lib(0,0,prefix=%{pythonprefix})')
| will return /usr/lib/.... on all archs for arch independent stuff
|
| %pyexecdir %(python -c 'from distutils import sysconfig; print
sysconfig.get_python_lib(1,0,prefix=%{pythonprefix})')
| will return /usr/lib{,64}/... for arch dependent stuff
|
|

This looks better.

The point of the object is that we SHOULD have macros for this, it's
completely synonymous with the existing Perl macros.  I don't
particularly care what the names are either so long as we agree them.

I'm also not too concerned if they make FC3, so long as we get them
agreed - then we can cut specs across at our convenience.

As you are aware, there are many projects which graciously provide specs
in their tarballs too.  By clearly defining the direction, these
providers can also migrate their specs at their leisure.

How about agreeing the definitive list and releasing it in the next most
convenient release of rpm?

Alan

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFBbQSeCfroLk4EZpkRAqlyAJ45vwpBQ0ecpOT94hcQKeL0Nh4UvQCeK3fV
arNqCn2N2EfwWdixNNod6l0=
=+SdU
-----END PGP SIGNATURE-----