Hello, I've been thinking about an DBP Manager for the Pyra recently and here are some features, that an DBP Manager could/should be able to do: Managing of DBP's and DEB's (and maybe even PND's, if there's an compatibility Layer) at the same time DBP packages replace/overwrite DEB packages in the Package list (as they are more Optimized) (DBP Maintainer specifies, which DEB package) "Link" to the DEB Package on the DBP "Page" The whole System can be Updated through the DBP Manager. Multiple User/Maintainer-shareable appdata tar's or Patches: For Example someone makes an Optimized Build of Libreoffice, but it only supports English or None Spell Checking, then the Maintainer or any User could add additional Language Plugins to LO which get saved into the Appdata Folder which the User/Maintainer then can Upload separately. So there could be an Appdata tar for English Spell Checking, for German Spell Checking and so on. This way, Emulator Settings and other things could be easily shared too. Maybe even Multiple Appdata directories? DBP Updates via Binary-Diff's? Change-logs separate from Package Description DBP Dependency resolving (For example for an Java DBP) Resolving between DBP/DEB? For Example an DEB Package depends on Java. This Package can then use the (Optimized) Java DBP. Or the Other Way around: DBPs can use the Optimized DEB Packages from our custom DEB Repo Cli and GUI interface. Moderator approval of DBP Packages to make sure that they don't contain Malware/Viruses. Maybe I'll hack something together with tcl/tk.