Repository files navigation

fpm-cookery is a very helpful wrapper around the excellentfpmrubygem, a gem that makes building packages amazingly easy. Cookeryextendsfpms powers by handling additional infrastructure requirementssuch as downloading files needed for the package build.

This repo contains some of the fpm-cookery recipes I've written for mypersonal use.

# get the code and install the prerequisitesgit clone https://github.com/deanwilson/unixdaemon-fpm-cookery-recipes.gitcd unixdaemon-fpm-cookery-recipesbundle install   # this installs fpm-cookery

Now we'll build one of the packages from our recipes. In this case we'llcreate agossDebian package.

cd gossbundle exec fpm-cook --target deb package... snip ...===> Created package: /home/dwilson/.../recipes/goss/pkg/goss_0.1.3_amd64.deb

You can now list the contents of the package -

dpkg -c pkg/goss_*.debdrwxrwxr-x 0/0               0 2016-04-05 23:36 ./usr/local/drwxrwxr-x 0/0               0 2016-04-05 23:36 ./usr/local/bin/-rwxrwxr-x 0/0         2323228 2016-04-05 23:36 ./usr/local/bin/goss

On Redhat you can build and confirm the package contents with

bundle exec fpm-cook --target rpm packagerpm -qvilp  pkg/goss*.rpm

This requires therpm-build to be present.

I have seen the occasional addition of extra files when buildingpackages on Fedora instances.

rpm -qvilp  pkg/*.rpm... snip ...drwxr-xr-x  2 root  root  0 Jan 18 17:05 /usr/lib/.build-iddrwxr-xr-x  2 root  root  0 Jan 18 17:05 /usr/lib/.build-id/3b

Setting the_build_id_links macro tonone seems to prevent thisbehaviour. In my case I've added it to the~/.rpmmacrosconfiguration file.

cat ~/.rpmmacros%_build_id_links none

Dean Wilson