import: npm-binary: Add a '--binary' option.

This changes the default behavior of the 'npm-binary' importer to prefer using
pristine sources from Git when available, along with attempting to build the
package.  It adds a '--binary' option to the importer to preserve the previous
behavior.

* guix/import/git.scm (get-tags): Export.
* guix/import/npm-binary.scm (<repository>): New JSON mapping.
(<package-revision>): Add a repository field.
(npm-package->package-sexp) [#:binary?]: New keyword.  Update doc.
Conditionally splice #:phases argument.
<normalize-git-url, sexpify-git-tag/maybe>: New nested procedures.
(npm-package->package-sexp) [binary?]: Expand origin conditionally to BINARY?.
(npm-binary->guix-package) [#:binary?]: New keyword.
(npm-binary-recursive-import): Likewise.
* guix/import/utils.scm (git->origin) [#:eager?]: New keyword.  Update doc.
* guix/scripts/import/npm-binary.scm (show-help): Document new --binary option.
(guix-import-npm-binary): Honor the new option.

Change-Id: I8e8c1c333faa8f5c96184ada064b63bdf2b4e165

1 files changed, 8 insertions, 7 deletions

diff --git a/doc/guix.texi b/doc/guix.texi
index d974a5cdf24..7950843c3c2 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -15733,13 +15733,6 @@ guix import npm-binary buffer-crc32@@1.0.0
 @end example
 
 @quotation Note
-Generated package expressions skip the build step of the
-@code{node-build-system}. As such, generated package expressions often
-refer to transpiled or generated files, instead of being built from
-source.
-@end quotation
-
-@quotation Note
 Currently, the generated package definition contains a phase to delete
 the development dependencies (@code{devDependencies}) from the
 @file{package.json} file, if there are such dependencies, to reduce the
@@ -15756,6 +15749,14 @@ Additional options include:
 Traverse the dependency graph of the given upstream package recursively
 and generate package expressions for all those packages that are not yet
 in Guix.
+@item --binary
+@itemx -b
+Import a binary NPM package.  This means preferring the use of a
+@url{https://registry.npmjs.org/} source origin, which typically bundles
+pre-built artifacts, along removing the @code{build} phase to avoid
+rebuilding such artifacts from source.  This should only be used as a
+last resort, as it is preferable building everything from source, to
+preserve referential transparency and the chain of trust.
 @end table
 
 @item opam