The zig cache dir used to be specified as an absolute path because of an
issue with build processes for local subdependencies changing the
current working directory incorrectly, this has since been fixed.
Additionally %{builddir} is a new construct that is not available under
EPEL, %{_builddir}/%{?buildsubdir} was considered however there is no
need for an absolute path at this time.
The generated objects should never match on different architectures due
to how the cache system is designed however there this may cause
confusion while debugging so its been put under %{_vpath_builddir}.
Specifying a direct cache name would be possible however I think
_vpath_builddir has become pretty well known to maintainers and would
best be suited for this.
`zig build --system` fails if the given path does not exist
this hasn't been an issue for river or ghostty since they pull in dependencies which makes zig create the given path, but ncdu doesn't have any dependencies.
the summary flag outputs a complete build summary of the whole build tree output in an orderly tree structure, very useful for inspecting what the build system actually did
- zig does not handle relative paths passed to the first process so we need to specify an absolute path
- system integration was accidentally broken by an extra % sign
- system flag was used on cache instead of package directory
