It allows us to retain the "aux" packages for subsequent rebuilds.
These packages are inserted in the "ports" step and removed in the
"packages" step.
May be subject to changes and tweaks, but works nicely when e.g.
rebuilding suricata.
In a batch build there are two check-plist errors, but they are
not easy to reproduce and otherwise hidden in the 200 MB log file:
>>> WARNING: The build provided additional info.
>>> Package list inconsistency for net/librdkafka (librdkafka)
>>> Package list inconsistency for www/squid (squid)
Move the print to the end so we can always see it.
Currently, when assigning multiple items to a LIST, the following works:
```
make ports PORTSLIST="port/a
port/b"
```
while the following would fail:
```
make ports PORTSLIST="port/a port/b"
```
Avoids spurious build errors for lang/rust on early shared LibreSSL/OpenSSL
build on the same machine. Also rebuilds benefit from this not wanting to
build rust at all if not necessary (go is not that bad).
check-plist is never executed, not even in QA scripts for FreeBSD,
but constantly being looked at, likely through Poudriere output.
In general such vital scripting should be executed in a standard
workflow, but to improve our own submissions just fold this into
the ports build manually.
With five consumers this makes sense nowadays. While here make the
distfiles fetch ignore PORT_IGNORE to download otherwise missing files
not found in the default flavour.
It's a lot of log content but somehow pkg wanting to bootstrap
into FreeBSD's 1.17 package during building is gone now which
sort of defeats the purpose if trying to fix this with more
debug output. *shrug*
Suspicously this seems to be caused by the ports tree now and
our previous code was working fine. The change is fine too,
but now we need to see which make target triggers this...
The /usr/sbin/pkg supports -N in the right way, but /usr/local/sbin/pkg -N
which is being invoked if /usr/local/sbin/pkg exists has other semantics
that sometimes makes this work and sometimes it doesn't. The manual page
mentions a weird workaround, but in the end if we assume that base pkg
execs local pkg we can almost certainly assume that it is bootstrapped and
usable.
No documentation for this as this is going to be reworked again.
Currenty though, during build tests editing these lines constantly
is not the best approach so at least now it works from the command
line.
For hotfixes it will start to build go and rust even if it does not
need it.
For the cases where e.g. suricata rebuild requires rust use the
non-packaged packages set or let rust build during dependecy build.
aux.conf harbours ports that are needed for the build and intermediate
package sets for testing and rebuilding, but that will ultimately be
removed from the sets when they are supposed to be uploaded to the mirror.
Franco Fichtner