unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Olivier Dion via <help-guix@gnu.org>
To: "(" <paren@disroot.org>, help-guix@gnu.org
Subject: Re: Guix as a native-inputs ?
Date: Tue, 02 Aug 2022 11:36:19 -0400	[thread overview]
Message-ID: <874jyu1wuk.fsf@laura> (raw)
In-Reply-To: <CLVL62BWSBYC.2F0AUGR9DL59W@guix-aspire>

On Tue, 02 Aug 2022, "(" <paren@disroot.org> wrote:
> On Tue Aug 2, 2022 at 2:41 PM BST, Olivier Dion wrote:
>> There seems to be an issue after all.  When building with Guix, my
>> script failed to access /var/guix/daemon-socket/socket with `guix
>> shell'.  I guess there's probably some way to make it available for the
>> build?
> You're in a container with access to nothing but the store and /tmp. It's
> not surprising that trying to access anything else doesn't work.

Right that was my though.  Do you thin there is a way to expose the
required files to the build container for accessing the Guix daemon?

I have at least another case -- a guix+guile declarative build system --
where I need to communicate with the Guix daemon in the build
container.

-- 
Olivier Dion
oldiob.dev


  reply	other threads:[~2022-08-02 15:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01 18:45 Guix as a native-inputs ? Olivier Dion via
2022-08-01 19:42 ` (
2022-08-02 13:41   ` Olivier Dion via
2022-08-02 13:44     ` (
2022-08-02 15:36       ` Olivier Dion via [this message]
2022-08-02 16:06         ` Julien Lepiller
2022-08-02 17:10           ` Olivier Dion via
2022-08-02 18:09             ` Julien Lepiller
2022-08-03 15:51               ` Olivier Dion via
2022-08-01 19:43 ` (
2022-08-01 20:34 ` Tobias Geerinckx-Rice
2022-08-01 22:05   ` Olivier Dion via

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=874jyu1wuk.fsf@laura \
    --to=help-guix@gnu.org \
    --cc=olivier.dion@polymtl.ca \
    --cc=paren@disroot.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.
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).