Re: poudriere and the user ... is it mostly a lost idea?

From: Rainer Duffner <rainer_at_ultra-secure.de>
Date: Wed, 15 Jan 2025 20:33:55 UTC
> Am 15.01.2025 um 20:30 schrieb John Nielsen <lists@jnielsen.net>:
> 
> 
> If you want to get a desktop up and running quickly then you can use the pre-built packages (which are signed and verified by default, clouds and unicorns notwithstanding).
> 
> If you choose to build all of your software locally that is 100% a supported option but it does put more responsibility on you, the user. When you get a build failure you are welcome to report it to the maintainer (listed in every single port file) and/or the appropriate mailing list (which -current is not, btw). Include the commands you are running and other configuration details as well as the exact error output.
> 
> Note, however, that the automated package build system already emails port maintainers on build failures and, choosing xfce as an example, I don’t see any such reports in the mailing list archives (https://lists.freebsd.org/archives/freebsd-xfce/). You can even view the results of the project’s package build system (which also uses poudriere) by following the instructions here: https://people.freebsd.org/~grahamperrin/pkg-status/
> 
> On a recent quarterly build I don’t see any failed or skipped ports related to the desktop environments you mentioned. (https://pkg-status.freebsd.org/beefy20/build.html?mastername=141amd64-quarterly&build=7b2027223baa)
> 
> I’d advise you to do more troubleshooting on your local system and provide some better details if you decide to ask for help in an appropriate forum, such as the freebsd-questions mailing list or the online forums at https://forums.freebsd.org/ or the mailing list(s) listed as maintainers for the ports you are having problems building.
> 
> Good luck,
> 
> JN


Recently, chromium got pulled in on my poudriere build as a dependency of some icinga sub-package.

That pulled in llvm19, which took I think 18 or 22 hours on the meager HP Gen 8 that poudriere is running on.

Then, after 24h, the build of chromium was erroring out.

I think you need to have reasonably recent and powerful hardware to do a build of a „full“ desktop.

My normal build is 20 hours for 2200 or so packages. Most time is spent on compiling llvm compilers….