[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Adding a subcommand "load-profile"
From: |
Roel Janssen |
Subject: |
Re: Adding a subcommand "load-profile" |
Date: |
Wed, 29 Apr 2020 21:14:21 +0200 |
User-agent: |
Evolution 3.36.1 (3.36.1-1.fc32) |
On Wed, 2020-04-29 at 15:48 +0200, zimoun wrote:
> Dear Roel,
>
> On Wed, 29 Apr 2020 at 14:46, Roel Janssen <address@hidden> wrote:
>
> > > > If there is interest in having this as a "load-profile" subcommand, I
> > > > will
> > > > post
> > > > an initial implementation to the mailing list ASAP.
> > >
> > > Instead of another subcommand, I would suggest to add an option to
> > > "guix environment".
> > > Then an another further step should maybe combine "--load-profile" and
> > > "--ad-hoc" in order to create a temporary "augmented" profile.
> >
> > I would strongly prefer to keep it backwards-compatible for our local HPC
> > users.
> > Also, the "environment" command generates a new profile, whereas the
> > proposed
> > "load-profile" merely applies the environment variables of an existing
> > profile
> > to a newly spawned shell. I think the way they work differs enough to
> > warrant a
> > separate subcommand.
>
> I understand that you would like to keep backward-compatibility with
> your current tools and ease the switch for your users. But you could
> do so by replacing all the shell code in the 'guixr load-profile' by
> "guix environment --load-profile". :-)
Well, I want to get rid of all the shell code. Not replace it with less shell
code. :)
And cluttering everyone's environment on our cluster with a bash function that
figures out whether to emit "guix environment --load-profile" or another guix
command seems far from optimal too.
Kind regards,
Roel Janssen