tip for archers
steve at holmesgrown.com
Fri Mar 4 11:04:35 EST 2011
I haven't messed with this program yet but what I like to do with most
applications on my Arch systems is to make them into packages for arch
package and dependency tracking purposes; easier to remove later on
too. In that context, I can then make corrections to most programs to
use the correct python version. Most often, that means making a
change in the PKGBUILD script to force python programs to use python2
instead of python. That way, My symbolic links don't have to be
changed around. Frankly, if I do any python work, I want to have
normal access to the latest version and that is 3.1 now. Anyway, just
my idea and how I would approach things and I really love the Arch
Build System (ABS) building packages is so easy with this.
On Fri, Mar 04, 2011 at 05:22:04AM -0500, Chuck Hallenbeck wrote:
> Willem kindly posted about his digital audio editor, and I had some
> initial difficulty with it on arch linux. The difficulty came about
> because I installed ecasound and python, as instructed, but had already
> been using python2. The result was that a soft link to python2 was
> changed to point to python3, and the fix was to change it back again to
> point to python2.
> It's called life on the bleeding edge.
> Thanks to Willem for a neat tool.
> Chuck in Hudson.
> My website is hallenbeck.ftml.net, my Jabber ID is chuckh1 at jabber.org
> Speakup mailing list
> Speakup at braille.uwo.ca
More information about the Speakup