all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: David Thompson <dthompson2@worcester.edu>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] HACKING: Mention 'guix environment'.
Date: Sun, 23 Nov 2014 21:26:38 +0100	[thread overview]
Message-ID: <877fyl64u9.fsf@gnu.org> (raw)
In-Reply-To: <873899c07r.fsf@izanagi.i-did-not-set--mail-host-address--so-tickle-me> (David Thompson's message of "Sun, 23 Nov 2014 12:10:00 -0500")

David Thompson <dthompson2@worcester.edu> skribis:

> Just today I used 'guix environment guix' to quickly create a
> development environment for Guix hacking.  I figured it should be
> mentioned in the HACKING file to assist developers that happen to
> already by using a Guix system.
>
> WDYT?

Sure, please commit!  I thought I had done it, but no.

> +If you are building Guix on a system that already runs Guix, you can use 'guix
> +environment' to spawn a shell whose environment contains all of the necessary
> +packages without installing them to your user profile:
> +
> +  guix environment guix

This is true only when ‘guix’ refers to the development version, which
has the autotools etc. as inputs.

I think it would be nice to have a ‘--install’ option to specify
additional packages to add to the environment, so that one could do
(say):

  guix environment mpc -i autoconf automake libtool

and get a really complete development environment.

(We discussed this on IRC some time ago, but I think we had overlooked
this simple solution.)

WDYT?

Ludo’.

  reply	other threads:[~2014-11-23 20:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-23 17:10 [PATCH] HACKING: Mention 'guix environment' David Thompson
2014-11-23 20:26 ` Ludovic Courtès [this message]
2014-11-23 21:02   ` David Thompson
2014-11-24 20:00     ` Ludovic Courtès

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877fyl64u9.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=dthompson2@worcester.edu \
    --cc=guix-devel@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.