--==========6495980586202EF28B05==========
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

> An annoying side effect of the way that we support multiple versions
> of python is that "/usr/pkg/bin/python" doesn't exist, so scripts
> can't use the usual
> 	#!/usr/bin/env python
> trick to startup.  It's a hassle to have to edit your scripts to
> contain "python2p3" (or whatever).

Indeed.

> I have implemented a "meta package" in lang/Makefile which installs a
> symlink from /usr/pkg/bin/python to ${PYTHONBIN}.
> I've attached the files (to go into lang/python).

IMHO the "latest and greatest" should also install the "python" bin. (But=20
this is also controversial wrt to pkg/updates).

> Are they any objections to this?

Only one minor thing. IMHO should the PKGNAME reflect Python version it=20
links to. So, maybe something like:
PKGNAME =3D python${PYVERSSUFFIX}-link ?

Maybe be should wait with this until drocher@ is back. I'm pretty sure he=20
has an opinion on this, too.

Cheers,
Marc
--==========6495980586202EF28B05==========
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)

iD8DBQFAD9O77YQCetAaG3MRAvw1AJ0XeiKZLQ6SZz+qIhspmOo2zzdubgCfZK2V
JO0FuR8Y22fsV8RIvU8w5co=
=Vq5R
-----END PGP SIGNATURE-----

--==========6495980586202EF28B05==========--