I love the idea!

I'm getting ready to start working on my TTS system some more and the part that needs the most help is the install script. Even if I had a slick install script, there's still the issue of getting the script and the files it needs onto the empeg. Having a package manager in jEmplode would be sweet!

One feature I'd like to propose is that the package manager have a global config file that it stores on the empeg (perhaps editable remotely via GUI). This could store settings such as:
- default programs directory
- default data directory
- list of all packages installed (editable?)
- Other stuff that I can't think of now, but will seem obvious later.

With a global config file like this, each individual installer can then suggest the user's preferred dir for installation (and most users can just click next). With a list of installed packages, you can have dependencies, or just set settings based on what's available (e.g. emptriv may default to audible if TTSd is installed, else visual).