I used the ferringb branches. They use bzr, one of those decentralized versioning systems.
$ bzr get http://bzr.pkgcore.org/ferringb/snakeoil-devBuilding/install was fine for snakeoil-dev (installed with the --prefix=/usr/local). That works well enough. But pkgcore-dev itself had trouble building because it couldn't find snakeoil includes. You would presume that snakeoil is in /usr/local/include/snakeoil, but no, it's actually in /usr/local/include/python2.4/snakeoil. This is slightly weird, so I have to add an enviroment variable for gcc to pick it up:
$ bzr get http://bzr.pkgcore.org/ferringb/pkgcore-dev
$ CPATH=/usr/local/include/python2.4 python ./setup.py buildNow it compiles just fine. Also (in the case of installing to /usr/local), you need to add the package location to PYTHONPATH:
$ cat /etc/env.d/99pkgcoreThen it works fine for me without any goofy symlinks or running from the user directory like some kind of punk bitch (that's right).
PYTHONPATH="/usr/local/lib/python2.4/site-packages"
1 comment:
apparently I'm just a wanker and /usr/local is for fools.
But I like /usr/local
It's where I put shit I don't want in /usr/
Oh well, I suppose I can use masterdriverz ebuilds.
Post a Comment