Re: Poudriere: when fetching a package with porttree from a git source, the generation of logs is slow

Hello.

On 2026/04/12 0:06, Roger Marquis wrote:
> Is this new behavior for 'make fetch'?
It is about the -b of poudriere bulk.
In the current version, it seems that the following command is allowed to run even with poudriere, rather than poudriere-devel.

poudriere bulk -j src -p git -z pkgfetch -b "http://localhost/packages/src-default/" category/portname

The -b option allows non-official packages to be fetched using values containing colons like this.
And by setting up a web server to publish the packages created by poudriere, it can be used so that the packages are copied to other jail-porttree-set.
This URL hosts a package created by poudriere bulk -j src -p default.

And as an example of how to use it, the one I used recently is like this.

poudriere bulk -j src -p default audio/libopenshot-audio multimedia/libopenshot@all multimedia/openshot@all
poudriere pkgclean -j src -p git -z pkgfetch ports-mgmt/pkg
poudriere bulk -j src -p git -z pkgfetch ports-mgmt/pkg
poudriere bulk -j src -p git -z pkgfetch -b "http://localhost/packages/src-default/" -C -t audio/libopenshot-audio
poudriere bulk -j src -p git -z pkgfetch -b "http://localhost/packages/src-default/" -C -t multimedia/libopenshot@all
poudriere bulk -j src -p git -z pkgfetch -b "http://localhost/packages/src-default/" -C -t multimedia/openshot@all

The key is to use poudriere pkgclean, delete everything except the pkg, and then let it fetch.
And, for some reason, only pkg cannot be fetched, so we will run a check once to see if ports-mgmt/pkg exists.
Furthermore, packages whose dependencies have been broken will be rebuilt, so the construction proceeds in multiple steps from the roots of the graph.

So, since the fetch for this example package amounts to hundreds, I would like to avoid digging through the git log :)

Regards.