--6Jy4/gb9ZgnsEOX8
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Jan 22, 2004 at 01:23:37PM +0100, Michal Pasternak wrote:

> It won't work as a binary package (except I want the Python version that
> build machine uses, which might not be exactly the one).=20
>=20
> When installed, it doesn't allow me to change the version I choosed during
> "compile" time (I must have pkgsrc installed).
>=20
> So, I don't think it's worth to import that Makefile to pkgsrc. It doesn't
> fix anything, really.
>=20
> Such functionality (provide one, common name for one or more different
> versions of single package) should be provided by some lower layer of
> pkgsrc, in a generalised way, available for all packages.

I think the point of it was to be able to run random python scripts
rather than to help pkgsrc installed scripts... users (as opposed to
administrators) would generally expect to be able to run 'python' and
get at least some installed version...

g.


--6Jy4/gb9ZgnsEOX8
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFAD9AJluYOb9yiFXoRAl04AJ4jkjcGrAN/AjFRB7U6BeMurzCRlgCeKNOI
bf/lMhiV7A2xj5QZH8P4BC8=
=GgYq
-----END PGP SIGNATURE-----

--6Jy4/gb9ZgnsEOX8--