all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: 01/01: guix: node-build-system: Use guile-json instead of a custom parser.
Date: Sun, 14 Jul 2019 20:19:18 +0200	[thread overview]
Message-ID: <20190714201918.6794a007@sybil.lepiller.eu> (raw)
In-Reply-To: <87blxw68f8.fsf@gnu.org>

Le Sun, 14 Jul 2019 15:40:43 +0200,
Ludovic Courtès <ludo@gnu.org> a écrit :

> Hi Julien,
> 
> guix-commits@gnu.org skribis:
> 
> > commit 8eb0ba532ebbebef23180e666e0607ea735f9c1a
> > Author: Julien Lepiller <julien@lepiller.eu>
> > Date:   Sun Jul 14 14:50:21 2019 +0200
> >
> >     guix: node-build-system: Use guile-json instead of a custom
> > parser. 
> >     * guix/build/json.scm: Remove file.
> >     * Makefile.am: Remove it.
> >     * guix/build/node-build-system.scm: Use (json parser) instead
> > of (guix build json).
> >     * guix/build-system/node.scm: Idem.  
> 
> This commit log doesn’t spell out all the variables and entities that
> were modified.  Please consider doing it next time, for clarity.
> 
> > +++ b/guix/build-system/node.scm
> > @@ -18,7 +18,6 @@
> >  
> >  (define-module (guix build-system node)
> >    #:use-module (guix store)
> > -  #:use-module (guix build json)
> >    #:use-module (guix build union)
> >    #:use-module (guix utils)
> >    #:use-module (guix packages)
> > @@ -27,6 +26,7 @@
> >    #:use-module (guix build-system)
> >    #:use-module (guix build-system gnu)
> >    #:use-module (ice-9 match)
> > +  #:use-module (json parser)
> >    #:export (npm-meta-uri
> >              %node-build-system-modules
> >              node-build
> > @@ -40,8 +40,8 @@ registry."
> >  (define %node-build-system-modules
> >    ;; Build-side modules imported by default.
> >    `((guix build node-build-system)
> > -    (guix build json)
> >      (guix build union)
> > +    (json parser)  
> 
> The effect of this change is to import the (json parser) from the host
> side into the build side.
> 
> As a result, if I have installed Guile-JSON 1.2 and you have
> Guile-JSON 3.1, we’ll end up building different derivations (and one
> of them won’t build :-)).
> 
> The solution here would be to do the equivalent of ‘with-extensions’
> for gexps.
> 
> However, given that that’s annoying to do without gexps, and given
> that the plan is to move build systems to gexps Real Soon, I’d be in
> favor of simply reverting this commit and using the custom JSON
> parser.  We can add a TODO/FIXME explaining that we’ll replace it
> with Guile-JSON as soon as build systems are rewritten to use gexps.
> 
> How does that sound?
> 
> Apologies if I overlooked it in your initial patch submission!
> 
> Thank you,
> Ludo’.

OK, sorry for pushing this patch then... I've reverted it in
a4bb18921099b2ec8c1699e08a73ca0fa78d0486. Thanks for the explanation!

  reply	other threads:[~2019-07-14 18:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190714125820.15568.58684@vcs0.savannah.gnu.org>
     [not found] ` <20190714125821.1CA192088F@vcs0.savannah.gnu.org>
2019-07-14 13:40   ` 01/01: guix: node-build-system: Use guile-json instead of a custom parser Ludovic Courtès
2019-07-14 18:19     ` Julien Lepiller [this message]
2019-07-14 18:27       ` Robert Vollmert
2019-07-15 12:25         ` Ludovic Courtès
2019-07-15 19:46           ` Robert Vollmert

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=20190714201918.6794a007@sybil.lepiller.eu \
    --to=julien@lepiller.eu \
    --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 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.