I think that the problem with programming directly on the Pandora to "check it has all the libraries" would actually work against you. No doubt you'd have development libraries on the thing in order to program in the first place, and hence something might work perfectly on YOUR Pandora but not on other people's without installing some random libraries. And anyone trying to take your source and recompile would no doubt end up missing some critical header file, or library version, and fail to do so. You're not going to want to wipe your Pandora / SD Card to get it back to a clean state.
This is why I like to keep my programming-target clean. Otherwise you run the risk of missing off libraries, compiling dynamically against different library versions etc. without realising.
When I do stuff on my GP2X, I program on a PC and then make myself manually transfer just the files I've changed and test the new version. Every few versions, I also make a clean dir and copy across what I "think" I need. The amount of times I've missed off a vital PNG, font, or other dependency... and I even have scripts to build a distributable version because of the dependencies - doing a test on a clean machine /folder means that I spot the problem and end up tying it into my usual scripts.
Luckily, I stick to one version of the SDL libraries, one version of glibc and one version of gcc otherwise it would turn into an absolute nightmare.
This is one of the problems I see with Pandora - my Linux PC's already have a bit of dependency hell - the dependency tracking on a portable device that may not always be connected to the Internet is a bit of a turn-off for me. I want to just download a hundred games, slap them on something and test them once I'm on the move, like I do with my GP2X. I don't want to have to wait until I can get somewhere with WiFi to download library X to make the games work. I can see a lot of programmers getting lazy with this and we'll end up with several programs needing packages X, Y and Z.
Sure, there'll be a package tracker with full dependency tracking either at release or slightly later but I quite like that the GP2X is a static target and "wipes itself clean" on every boot.