Re: Local ports [Was: Re: mail/postfix and mail/postfix-current missing on ports section]

From: Muhammad Moinur Rahman <>
Date: Mon, 27 Dec 2021 17:29:42 UTC
That’s one way of doing it but preferred way is a bit different as the upstream is modified and there might be merge conflicts while updating the tree. You have to use poudriere-devel and the overlay feature. So let’s say that I have a private repos of ports in github.

So what I do is:

poudriere ports -c -p default <USE OTHER OPTIONS AS REQUIRED>
poudriere ports -c -p default -U -p local -m git
poudriere bulk  -j 130 -O local <CATEGORY/PORTNAME>

The example is arbitrary and do not try to find the repositories please. Most of my overlay trees are for the orgs I work for which are not publicly available. But normally just adding a <CATEGORY/PORTNAME> in the root of the git repo is enough.

Kind regards,

> On 27 Dec 2021, at 17:58, Mel Pilgrim <> wrote:
> On 2021-12-19 8:33, Roger Marquis wrote:
>> On a similar note: is anyone is maintaing a local/custom port in
>> Poudriere or know where that might be documented?
> I do. I have a private repo in $PORTSDIR/local.  It's checked out on top of a poudriere ports tree and connected to the build system with:
> in make.conf.  You'll also want:
> /local/*
> in $PORTSDIR/.git/info/exclude to avoid poudriere ports -u complaining about a dirty tree.
> I tried using the overlays feature, but it has race conditions with the shorthand mechanisms that make complex port skeletons easy to maintain.