On 30/6/26 23:09, Hugo Buddelmeijer wrote:
That is, I can now, on e.g. my python-team checkout do
```
guix build -k -m my-favorite-manifest.scm # Many failures
guix build -m manifest-store.scm -r python-team-root
```
and then `guix gc` for unrelated reasons, keeping my progress.
No that does not work, because `guix build -r` only creates a root for
the last package that is built.
So I tried
guix shell -m manifest-store.scm -r python-team-root
but that does not work because several of the packages in that manifest
conflict. (Because it contains every package of the tip of python-team
that are already in the store, about 2700 packages.)
Anyone know a better approach?
I got to the point that I now have an exact list of thousands of
packages / store items that I do not want to have garbage collected, but
many are not live. Anyone an idea on how to proceed?
Should I create a root for each package?
I guess that should work. But then I will have thousands of roots that
I need to keep track of.
This is really limiting my Guix contributions, because if I just 'guix
gc', I have to spend another week getting back to having the python-team
branch rebuild.
But I'll soon run out of disk space if I don't `guix gc` to remove
builds from outdated python-team branches.
How does the rest of you handle this?
Hugo
