- Required tools
- Create a package
- Build a package
- Build the complete repositories
- Misc documentation
amkecpak is just an anagram of makepack (for Make Package).
I’ve implemented this set of Makefiles and script to more easily build .deb and .rpm packages.
I found that packaging .deb or .rpm is a little annoying for various reasons:
- I’ve limited memory and I could not remember all the options of rpmbuild and dpkg-buildpackage. I deeply prefer having simple, easy to remember commands like make deb or make rpm.
- I also wanted to build several packages in parallel easily.
- I wanted to avoid upstream sources recovery by hand as it’s somewhat annoying.
- I wanted to be capable to easily update my packages if a new upstream version is available.
- I didn’t want huge build dependencies for this build system, only usual tools like make, tar, posix shell...
- I didn’t want to mask the actual complexity of packaging software properly, I wanted to keep most of the knobs of regular .deb or .rpm packaging.
To achieve that, I used a set of Makefiles (for the parallel build capacity, the error handling, and the delta (re)build capacity). Plus some basic helper scripts to help with upstream source recovery, package initialization, or determining OS version.
I’ve also stolen some patterns I really liked from Gentoo.
Most upstream normalize how they ship sources. It’s generally a tar.gz file with a fixed pattern like <NAME>-<VERSION>.tar.gz, this pattern is even automatically implemented by hosting solution like GitHub.
Consequently it’s relatively easy to “templatize” a download URL with a $(VERSION) variable, this variable could also be used for setting the package version. This is generally how .ebuild files in Gentoo point to their respective upstreams.
Another thing I liked was that they keep a manifest file with the hashes of upstream sources. It permits to have a safe guard against modification of an existing upstream release, gaining some basic guaranties about build reproductibility and avoiding surprises...
Also the recovery of the upstream sources in Gentoo .ebuild files is a clearly distinct step from the build and install steps, no call to pip or wget in the middle of a compilation.
I’ve copied these ideas in this build “infrastructure”.
Amkecpak, a makefile based packaging framework.
|Doc:||Documentation on ReadTheDoc|
|Author:||Pierre-Francois Carpentier - copyright © 2015|
Packaging documentation in a nutshell¶
# Install the packaing tools $ apt-get install make debhelper reprepro # or $ yum install rpm-sign expect rpm-build createrepo make # Init a package foo $ ./common/init_pkg.sh -n foo $ cd foo/ # Implementing the package $ vim Makefile $ vim debian/rules ; vim debian/control $ vim rpm/component.spec # Help for the various targets $ make help # Building the packages $ make deb $ make rpm $ cd ../ # gpg key generation (one time thing) $ gpg --gen-key # Building the repositories # Use ERROR=skip to ignore package build failures and continue building the repo $ make deb_repo -j 4 # ERROR=skip $ make rpm_repo -j 4 # ERROR=skip
If you need more information, read the detailed documentation.