From: Phil <phil@beadling.co.uk>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>, help-guix@gnu.org
Subject: Re: Replacing python venv - environment or profile?
Date: Wed, 25 Nov 2020 20:35:18 +0000 [thread overview]
Message-ID: <857dq9qint.fsf@beadling.co.uk> (raw)
In-Reply-To: <87y2iqba88.fsf@web.de>
Much appreciated Arne - lots of interesting stuff on your website - a few
comments below too.
Dr. Arne Babenhauserheide writes:
> As far as I see it, guix environment is what you get from a virtualenv,
> plus a good deal more. I start more complex programs nowadays by pulling
> in their dependencies in a small startup file. The following is my
> actual command for running IntelliJ with custom libraries and the
> correct libstdc++:
>
> exec -a "$0" guix environment --ad-hoc openjdk@14 openjdk@14:jdk gcc-toolchain@10.2 -- bash -c "LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/home/arne/.guix-profile/lib:$(realpath ~/.guix-profile/lib/libsqlite3.so):/gnu/store/qj38f3vi4q1d7z30hkpaxyajv49rwamb-gcc-10.2.0-lib/lib/:."' IDEA_JDK="$(dirname $(dirname $(realpath $(which java))))" exec -a "$0" bash -x idea-IU-193.6911.18/bin/idea.sh'
Cool so Intellij starts up inside it's own environment with specific
toolchain and JDK requirements.
One question - is there any reason to use 'guix environment' rather than
have a profile setup with packages you need that you could then source
and start idea.sh from?
next prev parent reply other threads:[~2020-11-25 20:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 17:22 Replacing python venv - environment or profile? Phil
2020-11-24 20:44 ` zimoun
2020-11-25 20:21 ` Phil
2020-11-25 22:00 ` zimoun
2020-11-24 23:34 ` Dr. Arne Babenhauserheide
2020-11-25 20:35 ` Phil [this message]
2020-11-25 14:37 ` Christopher Lam
2020-11-25 15:36 ` zimoun
2020-11-25 22:54 ` Christopher Lam
2020-11-25 23:09 ` zimoun
2020-11-29 20:34 ` Maxim Cournoyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=857dq9qint.fsf@beadling.co.uk \
--to=phil@beadling.co.uk \
--cc=arne_bab@web.de \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).