I believe I now have an effective FreeBSD package manifest creator. It will be included in the next release of libDwm.<\/p>\n
I need this for the cases where I want to build a FreeBSD package for distribution without using ports. I have my own needs for this, but there are other cases where it makes sense to have this kind of functionality. For example, when you need to distribute data or configuration files. Heck, even packaging your shell initialization and other rc files from your home directory. Or in my case, packaging small things on a Raspberry Pi where I don’t have ports installed.<\/p>\n
The program inside libDwm is called ‘mkfbsdmnfst’. It’s in libDwm because I intend to use it for packaging libDwm and the support classes are in libDwm.<\/p>\n
It will read a template manifest file before reading files from a staging directory. This template file is in manifest format, though it also allows comments. Having the template allows the stuff that doesn’t change to be put in one place. Another benefit is that you can prepopulate parts of the ‘files:’ section. For example, when you have a binary that you want to be setuid root when the package is installed, you can use a line like this in the ‘files:’ section:<\/p>\n
\r\n\/usr\/local\/sbin\/evilsetuidprog:{uname:root,gname:wheel,perm:04555}\r\n<\/pre>\nI check that all files in the manifest exist in the staging directory, so that you will receive an error message if you have a manifest with files that don’t exist.<\/p>\n
More in a later post after I’ve written the manpage.<\/p>\n","protected":false},"excerpt":{"rendered":"
I believe I now have an effective FreeBSD package manifest creator. It will be included in the next release of libDwm. I need this for the cases where I want to build a FreeBSD package for distribution without using ports. I have my own needs for this, but there are other cases where it makes … <\/p>\n