GNU bug report logs - #51838
[PATCH 00/11] guix: node-build-system: Support compiling add-ons with node-gyp.

Previous Next

Full log

Message #407 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Philip McGrath <philip <at> philipmcgrath.com>
To: Pierre Langlois <pierre.langlois <at> gmx.com>
Cc: 51838 <at> debbugs.gnu.org, guix-patches <at> gnu.org
Subject: Re: [bug#51838] [PATCH v3 31/43] gnu: Add node-bindings.
Date: Sun, 12 Dec 2021 16:20:35 -0500

On 12/12/21 10:57, Pierre Langlois wrote:
>> +    (home-page "https://github.com/TooTallNate/node-bindings")
>> +    (synopsis "Help for loading your native module's @code{.node} file")
>> +    (description "Throughout the course of Node's native addon history, addons
>> +have ended up being compiled in a variety of different places, depending on
>> +which build tool and which version of @code{node} was used.  To make matters
>> +worse, now the @code{gyp} build tool can produce either a @code{Release} or
>> +@code{Debug} build, each being built into different locations.  This module
>> +checks @emph{all} the possible locations that a native addon would be built
>> +at, and returns the first one that loads successfully.")
> 
> I see the upstream description is prefaced with:
> 
> --8<---------------cut here---------------start------------->8---
> This is a helper module for authors of Node.js native addon modules. It
> is basically the "swiss army knife" of require()ing your native module's
> .node file.
> --8<---------------cut here---------------end--------------->8---
> 
> I'd suggest to just use this as the description, I'm not sure we need to
> mention node's addon build system history here.

Yes, I like that better.

-Philip

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.