Zen

Translation

mkdir -p "$GUIX_EXTRA_PROFILES/my-project"
=$HOME/.guix-extra-profiles
mkdir -p "$GUIX_EXTRA_PROFILES"/my-project/guix/bin/ # if it does not exist yet
guix package --manifest=/path/to/guix-my-project-manifest.scm \
--profile="$GUIX_EXTRA_PROFILES"/my-project/my-project
English type: example
GUIX_EXTRA_PROFILES=$HOME/.guix-extra-profiles
mkdir -p "$GUIX_EXTRA_PROFILES"/my-project # if it does not exist yet
guix package --manifest=/path/to/guix-my-project-manifest.scm \
--profile="$GUIX_EXTRA_PROFILES"/my-project/my-project
194/2370 · 237

Sign in to save the translation.

English Swedish Actions
Isolation: Programs from one profile will not use programs from the other, and the user can even install different versions of the same programs to the two profiles without conflict.
 
Deduplication: Profiles share dependencies that happens to be the exact same. This makes multiple profiles storage-efficient.
 
Reproducible: when used with declarative manifests, a profile can be fully specified by the Guix commit that was active when it was set up. This means that the exact same profile can be @uref{https://guix.gnu.org/blog/2018/multi-dimensional-transactions-and-rollbacks-oh-my/, set up anywhere and anytime}, with just the commit information. See the section on @ref{Reproducible profiles}.
 
Easier upgrades and maintenance: Multiple profiles make it easy to keep package listings at hand and make upgrades completely frictionless.
 
Concretely, here follows some typical profiles:
 
The dependencies of a project you are working on.
 
Your favourite programming language libraries.
 
Laptop-specific programs (like @samp{powertop}) that you don't need on a desktop.
 
@TeX{}live (this one can be really useful when you need to install just one package for this one document you've just received over email).
 
Games.
Spel.
Let's dive in the set up!
 
A Guix profile can be set up @i{via} a @dfn{manifest}. A manifest is a snippet of Scheme code that specifies the set of packages you want to have in your profile; it looks like this:
 
(specifications->manifest
'("package-1"
;; Version 1.3 of package-2.
"package-2@@1.3"
;; The "lib" output of package-3.
"package-3:lib"
; ...
"package-N"))
 
@xref{Writing Manifests,,, guix, GNU Guix Reference Manual}, for more information about the syntax.
 
We can create a manifest specification per profile and install them this way:
 
GUIX_EXTRA_PROFILES=$HOME/.guix-extra-profiles
mkdir -p "$GUIX_EXTRA_PROFILES"/my-project # if it does not exist yet
guix package --manifest=/path/to/guix-my-project-manifest.scm \
--profile="$GUIX_EXTRA_PROFILES"/my-project/my-project
mkdir -p "$GUIX_EXTRA_PROFILES/my-project"
"$GUIX_EXTRA"/my-project/guix/bin/guix package --manifest=/path/to/guix-my-project-manifest.scm --profile="$GUIX_EXTRA_PROFILES"/my-project/my-project
Here we set an arbitrary variable @samp{GUIX_EXTRA_PROFILES} to point to the directory where we will store our profiles in the rest of this article.
 
Placing all your profiles in a single directory, with each profile getting its own sub-directory, is somewhat cleaner. This way, each sub-directory will contain all the symlinks for precisely one profile. Besides, ``looping over profiles'' becomes obvious from any programming language (e.g.@: a shell script) by simply looping over the sub-directories of @samp{$GUIX_EXTRA_PROFILES}.
 
Note that it's also possible to loop over the output of
 
guix package --list-profiles
 
although you'll probably have to filter out @file{~/.config/guix/current}.
 
To enable all profiles on login, add this to your @file{~/.bash_profile} (or similar):
 
for i in $GUIX_EXTRA_PROFILES/*; do
profile=$i/$(basename "$i")
if [ -f "$profile"/etc/profile ]; then
GUIX_PROFILE="$profile"
. "$GUIX_PROFILE"/etc/profile
fi
unset profile
done
 
Note to Guix System users: the above reflects how your default profile @file{~/.guix-profile} is activated from @file{/etc/profile}, that latter being loaded by @file{~/.bashrc} by default.
 
You can obviously choose to only enable a subset of them:
 
for i in "$GUIX_EXTRA_PROFILES"/my-project-1 "$GUIX_EXTRA_PROFILES"/my-project-2; do
profile=$i/$(basename "$i")
if [ -f "$profile"/etc/profile ]; then
GUIX_PROFILE="$profile"
. "$GUIX_PROFILE"/etc/profile
fi
unset profile
done
 
When a profile is off, it's straightforward to enable it for an individual shell without "polluting" the rest of the user session:
 
GUIX_PROFILE="path/to/my-project" ; . "$GUIX_PROFILE"/etc/profile
 
The key to enabling a profile is to @emph{source} its @samp{etc/profile} file. This file contains shell code that exports the right environment variables necessary to activate the software contained in the profile. It is built automatically by Guix and meant to be sourced. It contains the same variables you would get if you ran:
 
guix package --search-paths=prefix --profile=$my_profile"
 
Once again, see @ref{Invoking guix package,,, guix, GNU Guix Reference Manual} for the command line options.
 

Loading…

User avatar None

String added in the repository
GUIX_EXTRA_PROFILES=$HOME/.guix-extra-profiles
mkdir -p "$GUIX_EXTRA_PROFILES"/my-project # if it does not exist yet
guix package --manifest=/path/to/guix-my-project-manifest.scm \
--profile="$GUIX_EXTRA_PROFILES"/my-project/my-project
mkdir -p "$GUIX_EXTRA_PROFILES/my-project"
"$GUIX_EXTRA"/my-project/guix/bin/guix package --manifest=/path/to/guix-my-project-manifest.scm --profile="$GUIX_EXTRA_PROFILES"/my-project/my-project
6 months ago
User avatar None

Source string changed
mkdir -p "$GUIX_EXTRA_PROFILES/my-project"
=$HOME/.guix-extra-profiles
mkdir -p "$GUIX_EXTRA_PROFILES"/my-project/guix/bin/ # if it does not exist yet
guix package --manifest=/path/to/guix-my-project-manifest.scm \
--profile="$GUIX_EXTRA_PROFILES"/my-project/my-project
6 months ago
Browse all string changes

Things to check

Mismatching line breaks

Number of new lines in translation does not match source

Reset

Glossary

English Swedish
Guix Guix guix Glossary
home hemkatalog guix Glossary
package guix Glossary
profile guix Glossary

17934654 String information

Source string description
type: example
Flags
no-wrap
Source string location
guix-git/doc/guix-cookbook.texi:4101
String age
6 months ago
Last updated
yesterday
Source string age
6 months ago
Translation file
po/doc/guix-cookbook.sv.po, string 883