Subject: Installing the latest Python as "python"
To: None <tech-pkg@netbsd.org>
From: Marc Recht <marc@informatik.uni-bremen.de>
List: tech-pkg
Date: 05/16/2003 15:26:38
--==========1779176916==========
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi!

The std. way to invoke the Python interpreter is: "#!/usr/bin/env python".=20
But, none of our lang/python* packages installs a ${PREFIX}/bin/python.=20
Only the pythonX.Y (eg. python2.2) binaries are installed. Because of the=20
"PYTHON_PATCH_SCRIPTS" Makefile knob (lang/python/application.mk) this=20
isn't a problem for pkgsrc managed packages, but it breaks 3rd party apps=20
which rely on the (std) "... env python". To fix this we should IMHO change =

the INSTALL_TARGET from the latest Python to "install" which will give us=20
"bin/python" and "bin/python2.2".

Regards,
Marc

mundus es fabula
--==========1779176916==========
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

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

iD8DBQE+xOcP7YQCetAaG3MRAiKWAJ4gJWyNw8MdnYBDWp2DUpjXpnolqwCeKxEu
8XdegjANatViR7Rt8YJMatA=
=Csz6
-----END PGP SIGNATURE-----

--==========1779176916==========--