Re: “Guix Profiles in Practice”

[Pierre Neidhardt <mail@ambrevar.xyz>]

[-- Attachment #1: Type: text/plain, Size: 1380 bytes --]

Hartmut Goebel <h.goebel@crazy-compilers.com> writes:

> Am 25.10.19 um 18:36 schrieb Thompson, David:
>> tool "just work."  Running 'guix develop' would check for a profile
>> symlink with some canonical name, for example '.guix-develop-profile'.
>> If it exists, it applies the environment variables and spawns a
>> subshell.  If it doesn't exist, it looks for a 'develop.scm' file
>> (canonical name TBD), builds the profile, symlinks it to
>> '.guix-develop-profile', and then does the prior steps.  The tool
>
> I like this idea :-)
>
> I suggest naming the file like the directory: .guix-develop-profile.scm
> (altough not sure whether the filenname should have the leading removed
> or not)

I think it's useful to support multiple directories since it's likely
that users will work on multiple projects.

See what I've done for Emacs-Guix.  The (configurable) file structure
looks like this:

- ~/.guix-extra-profiles/my-project
- ~/.guix-extra-manifests/my-project
- ~/.guix-extra-channels/my-project

The mapping is obvious.

Then I can do "guix-install-manifest", Emacs prompts me for a manifest
name in ~/.guix-extra-manifests (with completion), and does all the
necessary to install it in ~/.guix-extra-profiles.  It dumps the channel
specification in ~/.guix-extra-channels/my-project.

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]