On Samstag 21 November 2009, Wolfgang Rosner wrote:
be installed automatically along with 'python setup.py
install'. If it didn't: do you have any idea why?
could it be that I ran "make install"
instead of "python setup.py install" ?
"make install" invokes "python setup.py install". That shouldn't
have been it.
(sorry, I'm just getting used to Python, preferred
perl in earlier live)
first I thought it was due to the different python path structures.
standard on SuSE is
but the egg-laying machine seems to put stuff to
(maybe I could have reconfigured this, anyway)
Weird. Curious about the reasoning behind this.
However, gl_interop.py did not run until I did
(was PYTHONPATH="" before)
maybe this is since there is still the old python-opengl-2.0.1.09-224.1
...with-no-vertex-buffer-in-there in the way which is caught before.
But to figure it out I'm definitely lacking sufficient python experience.
There is an easy trick to find out what file path actually gets imported:
>> import pytools
hm, might give it a try.
I think best I could offer was be to prepare an own SuSE page with my
Sure--just add a subpage under
(like the one for Ubuntu)
It all comes down to different ways and places where
stuff is stored.
But I think my approach is not the best one, in the view back it were
better to configure new stuff so that it meets SuSE structure. Maybe.
Well, but this might break other dependencies?
Smells like big 'Baustelle'...
So if your expectation of quality on your wiki is not too high, I'll post
my experience there.
That's the whole point of a Wiki: information of questionable quality that
people improve as they use it. It's a knowledge retention tool.