Hi,
On Wed, 04 May 2022 at 15:46, Maxime Devos <maximede...@telenet.be> wrote:
> That's a use case, but this appears to be already implemented by "guix
> shell [-m manifest.scm]"? Though I suppose there's a use case for
> putting the manifests outside the project source code ...
Well, I miss two things: for one, ’guix shell’ creates a temporary
profile and thus not protected from GC so it can be boring to create
again and again the same profile depending on the frequency you are
working on the project vs the frequency “guix gc” is run. For two,
’guix shell’ does not guarantee the exact same profile depending if
’guix pull’ had been run in between.
Therefore, many use cases seem around, no?
Otherwise, even ~/.guix-profile is not useful at all since all could be
done with:
guix time-machine -C channels.scm -- shell -m manifest.scm
(what I do more than often ;-) but not protected from GC either).
For practical reasons, it seems easier to create some profiles and
“load” them (compose?) when required.
Cheers,
simon
