Not too long ago, we talked about the Freshen
script, which was in days past used to automatically run through all installed packages and update the out-of-date ones.
However, Freshen
was moved to legacy status because the state of dependency resolution in GoboLinux is currently such that package updates require a certain amount of nursing due to dependency-related build failures.
We have previously discussed perhaps using Runner
to construct a clean build sandbox when using Compile
.
Therefore I would like to ask how we might get started on using Runner
to create a clean sandbox for each Compile
run, initially as an option and later on (when core packages have had their dependencies cleaned up to the point where they are guaranteed to compile), we could potentially consider making it the default to the benefit of the health of GoboLinux and its community going forward?
As a corollary to this, once Compile
is switched to using Runner
sandbox functionality, we might also be able to re-assess whether to re-introduce an updated Freshen
to the GoboLinux toolkit?
In addition, I have not been able to find a description of the intended difference between the BuildDependencies
file and the Dependencies
file in build recipes? Buildtime-only for the former and Build+Runtime for the latter?
I would tend to think that this question matters in relation to a more strict sandbox build?
EDIT: I should note that with the recent addition of no-interactive-requirement-for-wired-ethernet-via-DHCP functionality, I will now be able to trivially test proposed Compile
/Runner
changes. So don’t be shy.