Port packpanda to Mac

(rdb) Hmm, could you maybe update the spec with some info how the directory structure would somewhat look, and how it would work?
To answer your questions:
"Is the official build of 1.6.0 from Panda3D.org universal?"
It should be. At least I tried to make it universal, let me know otherwise.
"Will we need to recompile Panda3D against the above Python?"
I hope not. If it is, we'll just compile the default build with the above Python, it should be compatible the other way.

(hypnos)maybe we should start a vote in the forums (using custom python, builtin to the panda3d package VS using systems python version):

with included python:
- can be bundled to a .app (which works universal, for 10.4 & 10.5)
- only a single installer for 10.4, 10.5 (less compile work for rdb)
- more up-to date version of python when running 10.4

without python:
- using systems python
- dont know anymore advantges, i am in favor of option "with python"

(fprimex) Updated with suggested filesystem layout.

(rdb) @hypnos: you should actually ask that at the other blueprint. But I'll add a vote on the thread soon.
@fprimex: Looks great! Thanks! There are two things:
(1) Is it necessary to include OpenAL? Isn't it included in the default OSX release?
(2) Wouldn't we put the Panda3D libs right away in the site-packages directory of Python? (at least a .pth file, IMHO) I mean, it's our own copy so we can directly stuff em there right?

(rdb) Marked superseded because packpanda will be deprecated in the upcoming release.