Implement simple packaging during build

[bradfa]

If we could generate simple packages, similar to how Slackware packages work (they're just basically tarballs), so that each thing we build generates a "-dev" package and a normal package, I think this would make managing builds easier to understand and make reworking mistakes less painful.

In the "-dev" packages would go header files, man pages, static libraries, and things which aren't needed for run-time. In normal packages would go anything needed for run-time execution such as shared libraries, executables, and config files. Then, for the build host sysroot, you install both the "-dev" and normal packages but for the target you only install the normal packages. If you mess up a package, or want to update it or change how it's built, you can just uninstall that package and build it again.

To keep things simple, there'd be no dependency tracking between packages or even between "-dev" and normal packages of the same name. It's still all manual so that it stays simple. The only tracking would be of which files belong to which package, so there is some metadata stored within each rootfs/sysroot but not very much.

The packaging should just be shell scripts which work both on busybox based systems and normal desktop/server distros in order to keep the dependencies of the packaging system low. A booting system with only a static linked busybox should be able to use the package manager scripts.

[bradfa]

Yes, I know, packaging systems are evil. But maybe the strengths can outweigh the weaknesses if we keep it simple enough?