-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Ryan Schmidt wrote:
Yes, that's right. A python port either uses python2.4 or it uses python2.5. If a python port could work with either, then two ports should be created. The one with the py- prefix is for python2.4 and the one with the py25- prefix is for python2.5. Then there are other ports like avahi which are not in the python category and don't have a py- or py25- prefix. These use either python2.4 or python2.5 as decided by the port author. I don't use any python software so I don't know the implications of changing the avahi dependency from py-gdbm to py25-gdbm. Perhaps the port author could comment. I'm Cc'ing him.
Hi, is there something we can do about these duplicated ports? As we have now a python-3.0 devel port there could be much more ports just for this version. Wouldn't be a bin:python:python24/25/30 better? The python ports (python24, python25, python30) could create a symbolic link named "python" so it should be there and can be checked. And for ports which need a specific version we could just check for that one (bin:python25:python25). What do you think about this? Simon - -- + privacy is necessary + using http://gnupg.org + public key id: 0x6115F804EFB33229 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iD8DBQFG3s4tYRX4BO+zMikRCnYtAKCYVS1aywuzi9180Pi2lg/m/qsXtgCgrqUQ hq3Rj7+gjre8KdJ2OOZd52U= =MVjU -----END PGP SIGNATURE-----