unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Thompson <dthompson2@worcester.edu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: guix-shell?
Date: Fri, 29 Aug 2014 22:03:54 -0400	[thread overview]
Message-ID: <87iolaivhx.fsf@izanagi.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87vbpc8vgr.fsf@gnu.org>

Ludovic Courtès <ludo@gnu.org> writes:

> David Thompson <dthompson2@worcester.edu> skribis:
>
>> I will implement 'guix shell' if I can get your opinion on the best
>> approach to take.  Would you tweak guix/scripts/build.scm to handle
>> the special case or export the necessary procedures and create a
>> guix/scripts/shell.scm module?
>
> The problem with a command that spawns a shell IMO is that it does not
> compose well: you get a new shell (which shell program is actually
> run?), and you can influence a running shell, or use it in a script,
> etc.
>
> So instead I would imagine a command like:
>
>   guix environment emacs
>
> which would build the dependencies of Emacs, and then output the search
> path as per ‘guix package --search-paths’, so that one can just source
> it and be done.
>
> In addition, one could do things like:
>
>   guix environment -l foo.scm

That sounds pretty good to me.  I don't have the process clear in my
head yet, though.  I need to read how our build script works more.

I think it would be nice to have a default file that guix environment
searches for if none is specified.  Tools like Ruby's bundler
automatically use a file called 'Gemfile'.  Perhaps guix environment
could look for an 'environment.scm' file by default?

-- 
David Thompson
Web Developer - Free Software Foundation - http://fsf.org
GPG Key: 0FF1D807
Support the FSF: https://fsf.org/donate

  reply	other threads:[~2014-08-30  2:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-22  9:22 Back from GHM Ludovic Courtès
2014-08-25 11:57 ` Amirouche Boubekki
2014-08-25 13:47   ` Thompson, David
2014-08-25 15:38     ` Amirouche Boubekki
2014-08-25 22:24     ` guix-shell? Ludovic Courtès
2014-08-26 11:32       ` guix-shell? David Thompson
2014-08-28 15:45         ` guix-shell? Ludovic Courtès
2014-08-26 12:14       ` guix-shell? David Thompson
2014-08-26 20:20         ` guix-shell? Andreas Enge
2014-08-26 20:31           ` guix-shell? David Thompson
2014-08-28 12:39             ` guix-shell? Amirouche Boubekki
2014-08-28 15:50         ` guix-shell? Ludovic Courtès
2014-08-30  2:03           ` David Thompson [this message]
2014-08-31 15:00             ` guix-shell? Ludovic Courtès
2014-09-18  2:22           ` guix-shell? David Thompson
2014-09-18  8:00             ` guix-shell? Ludovic Courtès
2014-09-21 17:25               ` guix-shell? David Thompson
2014-09-21 19:54                 ` guix-shell? Ludovic Courtès
2014-09-22  7:40                   ` guix-shell? 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

  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=87iolaivhx.fsf@izanagi.i-did-not-set--mail-host-address--so-tickle-me \
    --to=dthompson2@worcester.edu \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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 public inbox

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

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).