unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 37412@debbugs.gnu.org
Subject: [bug#37412] [PATCH 1/2] gnu: Add guix-data-service.
Date: Sun, 22 Sep 2019 11:18:35 +0100	[thread overview]
Message-ID: <87pnjs4osk.fsf@cbaines.net> (raw)
In-Reply-To: <87y2yofzqq.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1342 bytes --]


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

> Good morning, Chris!
>
> Christopher Baines <mail@cbaines.net> skribis:
>
>> * gnu/packages/web.scm (guix-data-service): New variable.
>
> Woohoo!  \o/
>
>> +      (inputs
>> +       `(("guile" ,guile-2.2)
>
> Guile should be ‘native-inputs’ because we use it for its compiler
> (which can act as a “cross-compiler” with ‘--target’).

This makes sense, but the scripts will still refer to the guile used to
build the package, so building for a different architecture won't work
right? Does the package somehow need to take as input two Guiles, one
for build time, and one for runtime?

>> +      (native-search-paths
>> +       ;; guile-git requires this to be set
>> +       (list (search-path-specification
>> +              (variable "GIT_SSL_CAINFO")
>> +              (file-type 'regular)
>> +              (separator #f)
>> +              (files '("etc/ssl/certs/ca-certificates.crt")))))
>
> It’s a bit of a workaround for
> <https://issues.guix.gnu.org/issue/22138>, isn’t it?  :-)
>
> What about either removing it, or adding an “XXX” to the comment?

I can't quite remember, I think I added that a long while ago when
trying to get the Guix service working. I'm not sure it's a great
approach. I'll add XXX to the comment though.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]

  reply	other threads:[~2019-09-22 10:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-15 18:18 [bug#37412] [PATCH 0/2] Add package and service for the Guix Data Service Christopher Baines
2019-09-15 18:21 ` [bug#37412] [PATCH 1/2] gnu: Add guix-data-service Christopher Baines
2019-09-15 18:21   ` [bug#37412] [PATCH 2/2] services: Add the Guix Data Service Christopher Baines
2019-09-16  7:53     ` Ludovic Courtès
2019-09-22 12:15       ` Christopher Baines
2019-09-15 20:45   ` [bug#37412] [PATCH 1/2] gnu: Add guix-data-service Alex ter Weele
2019-09-15 21:29     ` Christopher Baines
2019-09-16  7:48   ` Ludovic Courtès
2019-09-22 10:18     ` Christopher Baines [this message]
2019-09-22 21:04       ` Ludovic Courtès
2019-09-25  7:46         ` bug#37412: " Christopher Baines
2019-09-16  7:55   ` [bug#37412] " Ludovic Courtès
2019-09-22 10:10     ` Christopher Baines
2019-09-22 12:03 ` Christopher Baines
2019-09-22 12:03   ` [bug#37412] [PATCH 2/2] services: Add the Guix Data Service Christopher Baines
2019-09-22 21:11   ` [bug#37412] [PATCH 1/2] gnu: Add guix-data-service Ludovic Courtès
2019-09-24 19:34     ` Christopher Baines

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=87pnjs4osk.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=37412@debbugs.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).