Time for a new waf?

[James Browning]

On Saturday, December 21, 2024 11:53:14 AM Pacific Standard Time Hal Murray via 
devel wrote:
> Before the release?

Great Ghu no. After the release. If only because at least two functions 
in wafhelpers/options _need_ to be reworked. Notably the glue setting (cross) 
C and LD FLAGS as well as command line (un)define lists.

The only place I am aware of them being used is for the cross-armhf-build job; 
we do not need to fork it up more.
 
> What does this mean?  It doesnt happen if there is something to clean.
> 
> ...
> 'configure' finished successfully (6.202s)
> [murray at hgm raw]$ ./waf distclean
> 'distclean' finished successfully (0.010s)
> [murray at hgm raw]$ ./waf distclean
> /home/murray/ntpsec/raw/./waf:101: DeprecationWarning: Python 3.14 will,
> by default, filter extracted tar archives and reject files or modify their
> metadata. Use the filter argument to control this behavior.
>   for x in t: t.extract(x)
> 'distclean' finished successfully (0.004s)
> [murray at hgm raw]$

https://docs.python.org/3.14/library/tarfile.html#default-named-filters

tarfile in Python 3.14 is picky. Presumably there is a way tor restore previous 
behavior temporarily behind a NUSPI panel. It might be resolved in Waf 2.1.