From aba6876aba6bfeda7755b87b0fc9c32dd63aebf5 Mon Sep 17 00:00:00 2001 From: Vít Ondruch Date: Jun 22 2021 14:30:26 +0000 Subject: Fix formating broken by AsciiDoctor conversion. --- diff --git a/guidelines/modules/ROOT/pages/Node.js.adoc b/guidelines/modules/ROOT/pages/Node.js.adoc index 2e8fff3..5d22146 100644 --- a/guidelines/modules/ROOT/pages/Node.js.adoc +++ b/guidelines/modules/ROOT/pages/Node.js.adoc @@ -91,7 +91,7 @@ If you have further questions refer to the https://docs.fedoraproject.org/en-US/ == Using tarballs from the npm registry -The canonical method for shipping most node modules is tarballs from the npm registry. The `+Source0+` for such modules should be of the form http://registry.npmjs.org/[`+http://registry.npmjs.org/+`]`+/-/+``+-+``+.tgz+`. For instance: +The canonical method for shipping most node modules is tarballs from the npm registry. The `+Source0+` for such modules should be of the form http://registry.npmjs.org/[]`+/-/-.tgz+`. For instance: .... Source0: http://registry.npmjs.org/npm/-/npm-1.1.70.tgz @@ -172,7 +172,7 @@ The _nodejs_ package includes an automatic Requires and Provides generator that === Provides npm -It also adds virtual provides in the form `+npm(+``+)+` to identify modules listed in the npm registry (the module is listed at npmjs.org) . If a module is not listed in the npm registry, it must not provide this. Modules that aren't listed in the npm registry should set `+private+` to `+true+` in their `+package.json+` file. If not, you must patch `+package.json+` to include that. +It also adds virtual provides in the form `+npm()+` to identify modules listed in the npm registry (the module is listed at npmjs.org) . If a module is not listed in the npm registry, it must not provide this. Modules that aren't listed in the npm registry should set `+private+` to `+true+` in their `+package.json+` file. If not, you must patch `+package.json+` to include that. === Provides bundled @@ -244,7 +244,7 @@ Note that some modules may specify something like `+node-gyp configure && node-g `+node-gyp+` creates a shared object file with the extension `+.node+` as part of its build process, which should be located in `+build/Release+`. This file may be used as the main entry point for the library, or is utilized by JavaScript wrapper code included with the module. -If the shared object is used as the main entry point, it should be installed at `+%{nodejs_sitelib}/+``+/index.node+`. The `+require()+` function will automatically load this if there is no corresponding `+index.js+` or entry point defined in _package.json_ to override it. For example: +If the shared object is used as the main entry point, it should be installed at `+%{nodejs_sitelib}//index.node+`. The `+require()+` function will automatically load this if there is no corresponding `+index.js+` or entry point defined in _package.json_ to override it. For example: .... %install @@ -254,7 +254,7 @@ cp -p build/Release/index.node package.json %{buildroot}%{nodejs_sitelib}/foomod If the shared object is called by JavaScript wrapper code, the situation is slightly more complicated. -If the module uses the npm https://npmjs.org/package/bindings[_bindings_] module, the shared object file should be installed in `+%{nodejs_sitelib}/+``+/build/+``+.node+`, which is at the top of https://npmjs.org/package/bindings[_bindings_] search path and where `+node-gyp+` usually creates a symlink to wherever the real shared object file exists. For example: +If the module uses the npm https://npmjs.org/package/bindings[_bindings_] module, the shared object file should be installed in `+%{nodejs_sitelib}//build/.node+`, which is at the top of https://npmjs.org/package/bindings[_bindings_] search path and where `+node-gyp+` usually creates a symlink to wherever the real shared object file exists. For example: .... %install @@ -263,7 +263,7 @@ cp -p package.json wrapper.js %{buildroot}%{nodejs_sitelib}/foomodule/ cp -p build/Release/foomodule.node %{buildroot}%{nodejs_sitelib}/foomodule/build/ .... -If the module hardcodes `+build/Release/+``+.node+`, the module should be patched to use `+build/+``+.node+` instead, and upstream should be advised that they should use the https://npmjs.org/package/bindings[_bindings_] module, because their module could break when users use debug builds of node. +If the module hardcodes `+build/Release/.node+`, the module should be patched to use `+build/.node+` instead, and upstream should be advised that they should use the https://npmjs.org/package/bindings[_bindings_] module, because their module could break when users use debug builds of node. If the module uses it's own Makefiles to locate the shared object file(s) to a specific location, then those files should installed in that location.