From: "Ludovic Courtès" <ludo@gnu.org>
To: Steven Stallion <sstallion@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Manifest Hooks?
Date: Fri, 24 Jul 2020 18:33:08 +0200 [thread overview]
Message-ID: <87365g6fgb.fsf@gnu.org> (raw)
In-Reply-To: <CAGGHmKF4B5Mf=m+-6WYk0dGFrtT4qEK=b2aoSUBCciJQ-m2pXA@mail.gmail.com> (Steven Stallion's message of "Tue, 14 Jul 2020 19:57:27 -0500")
Hi,
Steven Stallion <sstallion@gmail.com> skribis:
> I've been looking into using manifests to help track some project
> dependencies and had a question for the list. Is it possible to add a
> shell hook similar to nix-shell when the packages specified by a
> manifest have been installed? In this specific case, I have a Python
> virtualenv I would like to activate when packages have finished
> installing without requiring additional scripting.
No, there’s no such thing. I guess you could tweak ~/.bashrc to do that
based on $GUIX_ENVIRONMENT but it’s not very elegant.
Besides, I’d be interested in your thoughts as to whether/how ‘guix
environment’ could be improved to make virtualenv unnecessary.
Thanks,
Ludo’.
prev parent reply other threads:[~2020-07-24 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 0:57 Manifest Hooks? Steven Stallion
2020-07-24 16:33 ` Ludovic Courtès [this message]
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=87365g6fgb.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=sstallion@gmail.com \
/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).