unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: jgart <jgart@dismail.de>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Running make inside a Guix Container From Outside
Date: Tue, 7 Sep 2021 17:47:28 +0200	[thread overview]
Message-ID: <CAJ3okZ3Rv_+tGY4fxwSq9tvX-atNsvFFBUcDtXtb=mxJ_+__Og@mail.gmail.com> (raw)
In-Reply-To: <20210906125732.GB27512@gac.attlocal.net>

Hi,

On Mon, 6 Sept 2021 at 18:58, jgart <jgart@dismail.de> wrote:

> ```
> #!/bin/sh
> git clone https://git.savannah.gnu.org/git/guix.git guix-3000
> cd guix-3000
> guix environment guix --container
> ./bootstrap
> ./configure --local-statedir=/var
> time make
> exit
> print "ready for hacking"
> ```

Instead, I would run something like

--8<---------------cut here---------------start------------->8---
#!/bin/sh

guix environment -C guix --ad-hoc bash -- bash -c \
     './bootstrap && ./configure --localstatedir=/var && time make'
guix environment -C guix
--8<---------------cut here---------------end--------------->8---

Well, this creates 2 temporary profiles.  If you want to save some
time, you can also pass '--ad-hoc bash' to the second environment even
if you do not you it.

Note that instead of '--ad-hoc', I would use '-m manifest.scm'
containing all the useful tools (Git, Emacs, etc.)

> Am I misusing `guix container exec`?

I do not know, I do not really use "guix container". :-)  Well, I
consider such subcommand as experimental. ;-)


Hope that helps,
simon


  reply	other threads:[~2021-09-07 15:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-06 16:57 Running make inside a Guix Container From Outside jgart
2021-09-07 15:47 ` zimoun [this message]
2021-09-10  5:24   ` jgart

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='CAJ3okZ3Rv_+tGY4fxwSq9tvX-atNsvFFBUcDtXtb=mxJ_+__Og@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=jgart@dismail.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).