Joerg Zinke wrote:
[...]
Python can co-exist in different versions at the same time. Why
should that not be possible for site-packages with our ports tree?
ACK, would be nice to be able install ports for different python
versions.
Maybe this issue could be solved by improving python.port.mk with a
additional variable which results in multiple install destinations for
the different versions or something like that:
PY_VERSIONS=2.3 2.4 2.5
in every python port.
that still leaves a few questions:
- how do we encode the version in the package name?
- we must make sure that the packages do not conflict. some python
packages have stuff in their PLIST that _will_ conflict, like
documentation or examples. The ports need to be changed to
put that in a subpackage.
Maybe a suffix would be a solution, e.g. for package <somepkg>
in version 1.2:
somepkg-1.2-python23.tgz
somepkg-1.2-python24.tgz
somepkg-1.2-python25.tgz
somepkg-1.2-common.tgz
At would at least not conflict to much with how we name FLAVORS.
regards,
joerg
- Marc
