unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: sirgazil <sirgazil@zoho.com>
To: mlell <mlell@posteo.de>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: How can I replace Python venv and pip with Guix?
Date: Tue, 04 Feb 2020 13:09:25 -0500	[thread overview]
Message-ID: <170116487ac.b7ccaa5d24989.1600771557397302786@zoho.com> (raw)
In-Reply-To: <6246e5281a43e838e35347f8413d6ed4@posteo.de>

 ---- On Tue, 04 Feb 2020 09:31:07 -0500  <mlell@posteo.de> wrote ----
 > Hi sirgazil,
 > 
 > > Well, the profile is created and persists, but, after deactivating the
 > > environment, how do I start an environment that uses that profile?
 > > 
 >
 > If you just want to create a profile following a manifest file, just use
 > 
 >     guix package --manifest="your-manifest.scm" -p 
 > /path/to/profile-folder
 > 
 > That said, the containerization features of `guix environment` can be 
 > handy in other cases, too.


Yes, I just skimmed through the "Guix Profiles in Practice" recipe in the Cookbook, and that seems to be what I should be using.

«[...] you can think of a profile as a kind of universal ‘virtualenv’ that can hold any kind of software whatsoever, not just Python software.»

I'll give it a try.

In my humble opinion, the "Guix Profiles in Practice" recipe should be converted into a section in the manual (called "Profiles"). I thought it was a nice overview.

Thanks again, Moritz.

  reply	other threads:[~2020-02-04 18:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-02 23:00 How can I replace Python venv and pip with Guix? sirgazil
2020-02-04  7:36 ` Moritz Lell
2020-02-04 13:00   ` sirgazil
2020-02-04 14:31     ` mlell
2020-02-04 18:09       ` sirgazil [this message]
2020-02-04  7:59 ` Tanguy Le Carrour
2020-02-04 14:26   ` sirgazil
2020-02-04 14:02 ` Ricardo Wurmus
2020-02-04 18:13   ` sirgazil
     [not found] <mailman.91.1580749212.18219.help-guix@gnu.org>
2020-02-03 21:09 ` Zelphir Kaltstahl
2020-02-03 22:56   ` sirgazil

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=170116487ac.b7ccaa5d24989.1600771557397302786@zoho.com \
    --to=sirgazil@zoho.com \
    --cc=help-guix@gnu.org \
    --cc=mlell@posteo.de \
    /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).