As the libpng package is special, with an animation patch, I decided to give the package a unique name, 'libpng_apng'. This is because the package manager has recorded a 'libpng' is already installed so won't list another package with the same name as a candidate for installation. It is also handy to have a different package name for an application like Firefox3 that needs the enhance libpng, so that the database entry for Firefox3 can list '+libpng_apng' as a dependency and it won't get confused with a non-patched libpng package.

I have also uploaded the 'gimp' package, just the main one so far, not the _DEV, _DOC or _NLS pckages.

I remade these packages from the expanded directories, using my improved 'dir2pet' and 'petspec' scripts. These are the database entries that got generated:

Note that each PET package has a 'pet.specs' file inside it, which also contains the database entry. This file is used by the 'petget' installed script if you had downloaded the PET package then clicked on it.
I mean, if you had not gone through the Puppy Package Manager, and just downloaded the PET package, then clicked on it in ROX-Filer. In such a case, 'petget' obtains all the information about the package from 'pet.specs' (technical note: if the package does not have a pet.specs, petget searches the /root/.packages/Packages-* database files for the package entry).