The ports collection has some serious issues

Dave Cottlehuber dch at
Fri Dec 16 07:54:25 UTC 2016

On Mon, 12 Dec 2016, at 17:20, Julian Elischer wrote:
> > Have you considered using things like poudriere that would allow you to build
> > your own repository with your own set of packages and options.
> >
> > You will benefit:
> > - ability to use pkg for your upgrades
> > - ability to use customize your packages
> > - safe rebuild process (in case of broken ABI)
> >
> > Best regards,
> > Bapt
> I'm actually slowly moving to this if I can work out how to specify my 
> own chroot image, and a few other things I need to tweak. (my own sets 
> of patches to add).

Hi Julian,

I've been doing this with poudriere + pkg + git for a couple of years
now very happily, using a lagging ports checkout (similar to the
quarterly branch but taken at our convenience), and git rebasing our
custom patches so they "float" up to the top. We're using it at now as well.

The guts of it is:

- use poudriere as usual but with a git-backed /usr/ports
- store custom patches in /usr/ports and push to until they get committed in FreeBSD
ports tree
- git rebase periodically to pull in shiny bits from
git:// master branch
- ansible pkg triggers a poudriere run whenever we add a new package to
the list
- these are made available via our pkg repo to our servers
- in practice, ansible is used to set up the whole stuff from scratch
including letsencrypt certs for the but these
are the pre-automation steps I started with.

Here are the raw notes from our wiki and that should be sufficient for
you to try this out on a test VM somewhere.  I assume I've forgotten
stuff or made errors but promise to blog it over Christmas with a longer

BTW I'm not exactly sure what you mean about a custom chroot image, but
I imagine you can fiddle with the poudriere base in
zroot/poudriere/jails/11_amd64 to your heart's content and it will be
used during the build.


More information about the freebsd-ports mailing list