Comment 4 for bug 953847

David or rdb,

Could either of you point me in the correct direction?
I (believe) I am fully up to the task of modifiying the PackageInfo.installPackage method to modify LD_LIBRARY_PATH, PATH, and DYLD_LIBRARY_PATH, and I will be able to test them on windows and linux (sadly I have no mac, someone else might be able to test that though)

In fact I thought this to be a rather easy task, however it proved me wrong quite quickly.
So my first thought was that if I modified the PackageInfo.py file under the 'direct' module, that I would be able to quickly edit and test the code. After that I built my p3d file again, ran it, and, well, the print statement I added into PackageInfo.installPackage never get's printed.

This is because (I believe) the entire direct/* tree is either compiled into or downloaded by the panda3d runtime, from runtime.panda3d.org, so I set out to build the panda3d runtime.

I used makepanda.py with the everything and runtime options, it gave me a working runtime, however it still fetches the direct/* tree from runtime.panda3d.org, which is of course, the code I'm trying to modify.

SO my questions:
How can I build the packages hosted on runtime.panda3d.org myself? And is the direct/* tree actually hosted there? Or where else does the runtime actually get those python modules?

Otherwise do you have any suggestion as to how I might go about fixing this bug? I realize both of you have much more relevant things to work on and fix, and that this bug is probably very low priority, so I'm only looking for a little guidance if you're able to help :)

Thank you,
~powerpup118