While the basic info needed for the PET format is generated (name, version, description), it doesn't (and can't) get some info, like it's dependency packages (you can automate some, but can't catch everything), if a package should be split (not into a DEV package, but one source into 2 different packages like "linux" and "linux-source"), and what architectures it can be built for.All the info is *generated* by src2pkg at package-creation time. That means it is always current, uniformly-formatted and correct -and that you don't have to supply it all."does not contain much info about the package"
The ppkg build scripts are designed to need manual modifications, but automate generic parts. It's tedious to always have to be generating them then merging the old version's options. They contain only essential information and info that removes the need for command-line options -transient or semipermanent options which can apply to any build are picked up from the conf file. The minimum code for a build script is just *5* lines, 1 of which is "}", and don't forget that sometimes you just need to fill in the source file, name, and version. You can even automatically download and compile a new version when you update one line. Where there are hundreds of source archives - just run `ppkg --pet -p *.pbuild.tar.gz` to compile everything.
See what I did there?
Ppkg doesn't generate anything, it gives you a template to start off with. If Ppkg was made for the PET format, packages would only have to fill in 8 fields - name, version, revision, description, category, arch, deps, and sources. In comparison, src2pkg needs 1.5 (sources and partially description), ignores 2 (arch and deps), and generates the rest (which only takes a minute to fill in to a PUPPYPKG file).
A PUPPYPKG file is easy to write, but allows packagers the power needed for "advanced" packages which need lots of patches, make flags, custom configuration files, symlinks, and moving files between split packages.
A big part of Ppkg is pBuild files - tarballs that can be compiled, which include any local sources that cannot be downloaded from the internet, without needing your own server to host the files.