Chase recent changes on ports-mgmt/sccache-overlay port and my poudlist-all.sh script.

This commit is contained in:
Tomoaki AOKI [aka Junchoon] 2024-06-16 16:23:35 +09:00
parent 614a1d1592
commit 8aa2be0d68

View file

@ -35,6 +35,8 @@ sccache daemonized process fails to acknowledge in time and causes timeout on po
This would NOT be a responsibility of sccache-overlay, but poudriere.
It should give much more time for sccache to acknowledge.
But unfortunately I couldn't have determined where in the poudriere to be tuned, including modifies to its sources.
Recently, the default timeouts on sccache-overlay side was raised by [ports-mgmt/sccache-overlay: Increase the timeout for server start](https://cgit.freebsd.org/ports/commit/?id=47e7d26def939bee65ef9b4ddb39fdda01fb19e9),
but still fails on certain situations.
If you want to activate sccache-overlay support regardless of above, you need to do below for preparation.<br>
`poudriere ports -c -p sccache -m null -M /usr/local/share/sccache/overlay`
@ -109,11 +111,15 @@ to (re)build updated ports in the list (and any ports depending on listed ports
Note that you should run the script everytime you update the ports tree not to miss new MOVED entry.
Otherwise, if any of ports you have in bare-metal environment are removed from ports tree, the list containing entries without sane origin (category/port) causes poudriere to error out and not starting actual builds.
And also, the script doesn't aware of FLAVORs.
<del>And also, the script doesn't aware of FLAVORs.
Just picks the origins of installed ports.<br>
But don't worry.
The list is just a text file, containing ports origins one-per-line.
But don't worry. <br></del>
The script automatically picks up FLAVOR used for builds. See its [README.md](https://brew.bsd.cafe/TomAoki/sh_scripts/src/branch/main/poudlist-all/README.md) and script itself for details.
So you need to edit or drop the flavor when you want to change its flavor to be changed, including to follow changes in default flaver.
The list generated is just a text file, containing ports origins one-per-line.
You can add "@flavor" at the end of the specific line.
Even more, if you want to specify multiple flavors for single origin, you can duplicate the line as needed.
### Dry run (See what's done without actual builds)