|
There are no real guides, just user experience and reworking efforts from other distributions.
Example:
pkgtools from Slackware is a set of scripts that create, unpack, install, remove, and update tarballed packages usually in .tgz or .txz format. They can use the dialog with ncurses packages to give a sort of UI, but it's not required. It also requires tar-1.13 be included alongside the current tar package.
pkgtools uses SlackBuild scripts with slack-desc description files and doinst.sh post-install scripts. It's very simplistic and offers no dependency resolution unless you craft the .info files and README files used by SlackBuilds.org that can utilize add-on tools like sbotools to create pseudo dependency resolution methods.
However, you will need intimate knowledge of how to use patches to make sure them with packages like glibc to make sure glibc doesn't perform a lock-in with ldconfig pointing at /tmp/package-glibc/lib and use /lib instead and other such issues. You will also need to possibly perform many reinstalls of other packages to keep re-resolving dependencies as things get added.
Often, I find it best to just keep pre-configured source packages in /usr/src ran with make clean on them. It's a lot easier.
LFS unofficially uses the fakeroot hint from Chapter 6 as a package management system, but in truth any system can be imported.
|
