Dear Kevin,
I really like the alias solution.
That said, the reason that pydonna.sh came into being is that I was
innocently trying to install some libraries as follows:
sudo apt-get install libunwind8 libicu55
In support of Micro$oft powershell on linux, and I got the errors I
associate with the package manager not having the right version of python
available when it invokes "python" in it's little script.
So in a blind rage I wrote pydonna.sh, symlinking it with
/usr/bin/pydonna. I ran it, seleceted "2.7" then ran the install again:
sudo apt-get install libunwind8 libicu55
...it worked fine, now I have powershell, for what that is worth.
Subsequently I re-invoked myself back to 3.5.
That said your idea of constructin an alias has genuine merit. My concern
it that for all I know the damn aptitude operates in it's own shell and
will ignore a local alias.
What do you think. I will cheerfully rewrite pydonna to be better
behaved if you think the alias trick will work.
Regards,
Paul
On Thu, 15 Dec 2016, Kevin Cole wrote:
Date: Thu, 15 Dec 2016 09:39:58 -0500
From: Kevin Cole <[email protected]>
To: Paul Flint <[email protected]>
Cc: David LaFreniere <[email protected]>,
Henry Rivera <[email protected]>, Eric Howard <[email protected]>,
Jeffrey Elkner <[email protected]>, Jeff Elkner <[email protected]>,
Vermont Area Group of Unix Enthusiasts <[email protected]>,
Adult Swim <[email protected]>
Subject: Re: How tired am I of the python version bug?
There's a frightening bit of code... This is how a package management
system gets hopelessly broken.
If you REALLY want to go down that road, may I suggest LFS (Linux From
Scratch) or at the very most, Slackware. For just about any other
distribution, "rm -rf /usr/..." is just a horrible thought, regardless
of whether or not it's merely a symbolic link. (I'm not sure I'd be
wild about it for Slackware even.)
Unless you have some compelling reason not to, why not just create an
alias, rather than stomp all over /usr like a berserker? i.e.
$ alias python='python3.4'
or whatnot, in your .bash_aliases (after uncommenting the stanza in
~/.bashrc that says you want to put your custom aliases in
.bash_aliases).
Kindest Regards,
☮ Paul Flint
(802) 479-2360 Home
(802) 595-9365 Cell
/************************************
Based upon email reliability concerns,
please send an acknowledgement in response to this note.
Paul Flint
17 Averill Street
Barre, VT
05641
