Re: [Plplot-devel] New test run on Debian woody

[Alan W. I. <ir...@be...>]

Thanks, Maurice, for the symlink suggestion which I will use as an interim
measure.

It turns out this python2 name was an artifact of a license dispute that
forced the Debian packager to clearly distinguish between the python2
product (whose early version was not GPL compatible) and python-1.5 (which
was compatible).  Fortunately, that license dispute has been resolved for
later python 2 products.  Thus, the Debian python packager intends to
replace both the python2 and python (1.5) package by one updated python
package (python 2.1, IIRC).  At that point the name of the executable will
be python again.  It is possible the time scale for this change will be
short, but we will just have to wait and see.

Alan

email: ir...@be...
phone: 250-727-2902	FAX: 250-721-7715
snail-mail:
Dr. Alan W. Irwin
Department of Physics and Astronomy,
University of Victoria, P.O. Box 3055,
Victoria, British Columbia, Canada, V8W 3P6
__________________________

Linux-powered astrophysics
__________________________

On Mon, 22 Oct 2001, Maurice LeBrun wrote:

> (I just returned from vacation)
>
> Alan W. Irwin writes:
>  > Some problems did show up for my new woody environment:
>  >
>  > (1) The python xw??.py scripts didn't work out of the box because Debian
>  > woody calls the command python2 to distinguish it from the python-1.5
>  > command which is still called python.  I tried alias so that executing
>  > python interactively actually did execute python2, but /bin/env python
>  > ignores the alias, and gets the old version.  (Numeric is not installed for
>  > that old version so it makes a mess.) The only way out I could see was to
>  > locally (not in cvs) edit all the xw??.py scripts to change the reference in
>  > the first line from python to python2.  I don't see any easy way around this
>  > name change. Unless somebody has a suggestion for an easy fix, I think we
>  > should write this off as a temporary Debian woody peculiarity which will
>  > eventually get fixed, and not make any changes to plplot.  This is
>  > something, however, that Rafael will have to deal with as the woody packager
>  > of plplot.
>
> I always use softlinks for this kind of thing.  Link `which python2` to
> ~/bin/python or even /usr/local/bin/python and make sure they come in your
> path before the old python and you're set.
>
> --
> Maurice LeBrun    mj...@ga...
>
> _______________________________________________
> Plplot-devel mailing list
> Plp...@li...
> https://lists.sourceforge.net/lists/listinfo/plplot-devel
>