Packaging Guide

Tips

• Consider the build a black box (as much as possible)
  • Only change inputs (configure args)
  • If it does things wrong that can’t be changed with inputs modify the outputs
  • Don’t fuck with the innards
  • Rationale: the maintainer will update the innards and your hacks will break
  • Rationale: we don’t know much about the innards: changes will have unforeseen consequences

Troubleshooting

• Check you are reading the right README. Sometimes projects have already updated the README on GitHub for the next release.

Resources

• Arch has a great Wiki maintained for >15 years https://wiki.archlinux.org/title/PHP_package_guidelines
• Linux from Scratch is basically a guide to what we do https://www.linuxfromscratch.org/blfs/view/svn/general/gobject-introspection.html
• https://tracker.debian.org/ (old “tracker”: https://packages.qa.debian.org/)
• [Stripping](http://www.muppetlabs.com/~breadbox/software/tiny/teensy.html)
• https://www.pkgsrc.org/
• vtool -show FILE.dylib can be useful
• https://github.com/Linuxbrew/brew/ have dealt with a lot of same issues as us
• https://github.com/macports/macports-ports
• https://snarky.ca/how-virtual-environments-work
• https://github.com/macports/macports-ports (recipes repo)