How all those dports get built

I’ve mentioned it before, but the tool ‘synth‘ is what DragonFly uses to build all the dports binaries – over 30,000 packages, though I’m typing that from memory and not from looking at a tool.  Anyway, the one part of the release process I’ve never touched was the package building – and now it’s documented.  This document is oriented towards DragonFly releases – but if you wanted to create your own package repo with custom options, this is the way to do it.

One Reply to “How all those dports get built”

  1. As a cautionary tale, building with synth can destroy your pkgng database and leave you with a system that has both a broken synth and pkgng setup. It’s a good tool, but be sure to backup and to read before using it.

Comments are closed.