On Thursday 26 June 2008 13:08:03 Jan Matějek wrote:
Will the python3 package include rpm macros, such as '%py3_sitedir'?
I didn't look into this yet. Probably not now, but we'll certainly add them later.
Unfortunately, the existing ones refer to 'python' instead of %{__python}, so it's not a simple matter of sticking a '%define __python /usr/bin/python3' in the spec. This leaves either creating a package macro file, redefining the macros in the rpm package, or defining the following in python3-* specs: %py_ver %(python3 -c "import sys; v=sys.version_info[:2]; print '%%d.%%d'%%v" 2>/dev/null || echo PYTHON-NOT-FOUND) %py_prefix %(python3 -c "import sys; print sys.prefix" 2>/dev/null || echo PYTHON-NOT-FOUND) Personally, I'd prefer the '%define __python /usr/bin/python3' method, but that would require a change to rpm.
Will there be a 'devel:languages:python3' project, or should Python 3 packages be placed in 'devel:languages:python'? If the latter, should new python3-*
I'm placing python3 into devel:languages:python
Excellent. I can't wait to try it.
packages be created, or should the existing packages be modified to generate both if %suse_version > 1100?
I don't think that it would make any sense. For one, if the rumors are true, then python2.x packages will need to be rewritten (automatically, but rewritten nevertheless) to work in python3.
I was under the impression that any code that was migrated to 3.x would run fine in 2.6, just not necessarily in 2.5 or below.
And for two, even if you managed to make one source work on both pythons, there's still the issue of dependency on python/python3, package name (python- vs. python3-) and all the little thingies. You would most likely end up with two unrelated specs for one package... and at that point you are better off with separate packages.
I wasn't proposing that binary packages should work for both. The bytecode is certainly different. I'm just wondering about cases where the upstream source is common. I guess linking python3-modulename to python-modulename would probably be best. -- James Oakley jfunk@funktronics.ca --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org