poudriere VS freebsd-ports

poudriere is a powerful port/package build and test system with a focus on package production and bulk building for FreeBSD. This easy-to-use, parallelized solution relies solely on the base system and can build the entire portstree. Supports building packages for different FreeBSD versions, and ensures compatibility with any package management tool by organizing packages in an identical layout to official mirrors. qci considers it a favorite tool.

poudriere(8) command synonyms: jail, jails … · Issue #1053 · freebsd/poudriere

95% of the time the only thing you have to do is install a package and enable the service. So what's the value in having a centralized repository of pre-configured images? Sure, if you want to roll out an image to thousands of servers - make an image using poudriere image](https://github.com/freebsd/poudriere/wiki/poudriere-image.8-devel) and send them out. It's not really any easier - and is definitely not better - to use an image that someone else made.

> pkg is an amazing system that beats dpkg or rpm

What's your reasoning for this statement? I find poudriere[1] handy for compiling one's own packages from ports configured to fit one's goals, but I see nothing outstanding in plain pkg.

It has issues when there's an IPv6 address up (even link-local) but no egress v6 routing. It would hang and wait for a timeout when an IPv6 address is selected from resolved addresses. After a timeout - pkg connects to v4 endpoint but if there's several packages to be downloaded, it can fall back to trying to connect to v6 with the next package.

On the other hand, I've recently had Ubuntu 22.04 register Python-related packages which were not successfully installed, resulting in all dpkg/apt/apt-get commands failing due to py3clean script throwing trackbacks, until /var/lib/dpkg/status was edited and these packages were in fact installed and then removed.

[1] https://github.com/freebsd/poudriere/wiki

poudriere-devel has a bug where it tries to delete the incorrect zpool when building a zfs image fails. There's a pull request that addresses it, but I have no idea when that will get merged. I also don't know how long it will be before there's a new poudriere release after it gets merged. The current ports version was last updated in 2022-09, so it could be months.

I use this with Poudriere to speed up my FreeBSD pkg host building multiple Sets of ports https://github.com/freebsd/poudriere/wiki/ccache

Also jails is a terrific concept with poudriere and bastille

https://github.com/freebsd/poudriere/wiki/ and more.

Agreed.

I don't think the PR reviewer is calling the author in the example, and provided useful info, pointing out the relevant example.

Also, the author notes:

> The very first comment in the thread from a reviewer was simply only one word: “Why?” - That’s it, just one word. Why did I do this? Why work with such old hardware? Why is the sky blue? How the hell am I to know the context of what they’re referring to when asking a one-worded question?

Its clear from https://github.com/freebsd/freebsd-ports/pull/189#discussion... that the author is asking why is this line needed, something a PR author should always be able to justify.

From https://github.com/freebsd/freebsd-ports/blob/main/UPDATING:

KDE: Update KDE Plasma Desktop to 5.26 · freebsd/freebsd-ports@d06d26f | https://cgit.freebsd.org/ports/commit/?id=d06d26f8c45e468021b1ec1def42fb1ce600a3dc

Say you really want to pin to Apache 2.5.54. Create a new empty repo, add a www/apache24 dir, and copy the files from that version of the ports tree into it.

They have not been stable

https://github.com/freebsd/freebsd-ports/commit/a43ec88422ee...

As for announcements: how would this information be delivered to you? :) Major breakages that impact users are expected to tracked in Ports (not pkgs) through review of /usr/ports/CHANGES and /usr/ports/UPDATING. If a port gets renamed (moved), you'll find it mentioned there, or possibly in /usr/ports/MOVED (not human-readable). You can view those on the GitHub mirror if you wish, since not everyone builds from Ports: https://github.com/freebsd/freebsd-ports

at https://github.com/freebsd/freebsd-ports/tree/main/chinese/chinese-calendar (for the port to FreeBSD) the files and Makefile are not too complex.