The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not update the repository.
Zen

Source string Source string

217/10000 · 217

This translation is currently locked.

English Actions
The following macros are defined for you:
|Macro |Normal Definition |Notes
|__nodejs |%\{_bindir}/node |The Node.js interpreter
|nodejs_version |e.g. 0.9.5 |The currently installed version of Node.js.
|nodejs_sitelib |%\{_prefix}/lib/node_modules |Where Node.js modules written purely in JavaScript are installed
|nodejs_sitearch |%\{_prefix}/lib/node_modules |Where native C++ Node.js modules are installed
|nodejs_symlink_deps |%\{_prefix}/lib/rpm/nodejs-symlink-deps |See <<Symlinking Dependencies>> below.
|nodejs_fixdep |%\{_prefix}/lib/rpm/nodejs-fixdep |See <<Correcting Dependencies>> below.
|nodejs_arches |%\{ix86} x86_64 %\{arm} |See #ExclusiveArch. This macro is provided by `+redhat-rpm-config+` in F19+ so it works with Koji properly.
|nodejs_default_filter |%global __provides_exclude_from ^%\{nodejs_sitearch}/.*\\.node$ |Filters unwanted provides from native modules. See <<Filtering Unwanted Provides>> below.
These macros are provided by the _nodejs-packaging_ package.
During `+%install+` or when listing `+%files+` you can use the `+%nodejs_sitelib+` or `+%nodejs_sitearch+` macro to specify where the installed modules are to be found. For instance:
%files
# A pure JavaScript node module
%{nodejs_sitelib}/foomodule/
# A native node module
%{nodejs_sitearch}/barmodule/
Using this macro instead of hardcoding the directory in the specfile ensures your spec remains compatible with the installed Node.js version even if the directory structure changes radically (for instance, if `+%nodejs_sitelib+` moves into `+%{_datadir}+`).
ExclusiveArch
The V8 JavaScript runtime used by Node.js uses a Just-in-Time (JIT) compiler that is specially tuned to individual architectures, and must be manually ported to any new architectures that wish to support it. Node.js packages must include an ExclusiveArch line that restricts them to only these architectures.
The `+%{nodejs_arches}+` macro is provided to make this easy, so pure JavaScript packages must use:
ExclusiveArch: %{nodejs_arches} noarch
Native (binary) packages must omit `+noarch+` and list only `+%{nodejs_arches}+` or the list of architectures as appropriate.
Bundled Licenses
The licenses of the bundled Node.js modules need to be in the spec file. If you are using our bundling script, they will be listed in `+<package>-<version>-bundled-licenses.txt+`. It is recommended that you include `+<package>-<version>-bundled-licenses.txt+` in the rpm.
Each time you update your package, you need to verify the bundled licenses against https://docs.fedoraproject.org/en-US/legal/allowed-licenses/[Fedoras Software License List]. Note that precompiled/minimized JavaScript may be packaged, but the requirement to verify the licenses also applies to it, see the :xref:JavaScript.adoc[JavaScript guidelines].
List all unique licenses on the License: line of your spec file. https://docs.fedoraproject.org/en-US/legal/license-field/#_basic_rule[Separate each license with the word "and"].
License: <license1> AND <license2> AND <license3>
...
Source3: %{npm_name}-%{version}-bundled-licenses.txt
...
%prep
...
cp %{SOURCE3} .
...
%files
%license LICENSE %{npm_name}-%{version}-bundled-licenses.txt
If you have further questions refer to the https://docs.fedoraproject.org/en-US/packaging-guidelines/LicensingGuidelines/[Fedora Licensing Guidelines].
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 https://registry.npmjs.org/[]`+<modulename>/-/<modulename>-<version>.tgz+`. For instance:
Source0: https://registry.npmjs.org/npm/-/npm-1.1.70.tgz
This method should be preferred to using checkouts from git or automatically generated tarballs from GitHub.
These tarballs store the contents of the module inside a `+package+` directory, so every package using these tarballs should use the following in `+%prep+`:
%prep
%setup -q -n package
Using tarballs for bundling
It is prefered to use tarballs for bundling node module dependencies. These tarballs should be independent from the main package source. There should be two tarballs. One for the binary, runtime package. One for testing while the package builds. This creates a smaller installed package.
These tarballs store the bundled modules in a directory called node_modules_prod, and node_modules_dev.
If your packages does not need one of the tarballs, then change these instructions accordingly. If it does not need the prod tarball, remove `+Source1+` plus the `+%build+` and `+%install+` sections. If it does not need the dev tarball, remove `+Source2+` and the `+%check+` section.
Note1: The setup of the prod and dev tarballs will soon become a macro. At the time of this writting, they are not.
Note2: The tarball with the dev dependencies needs to be unpacked in +%check+ and not in +%prep+ to avoid accidentally bundling the unpackaged dependencies that are only needed for testing.
...
Source1: %{npm_name}-%{version}-nm-prod.tgz
Source2: %{npm_name}-%{version}-nm-dev.tgz
...
%prep
...
# Setup bundled runtime(prod) node modules
tar xfz %{SOURCE1}
mkdir -p node_modules
pushd node_modules
ln -s ../node_modules_prod/* .
ln -s ../node_modules_prod/.bin .
popd
...
%install
...
# Copy over bundled nodejs modules
cp -pr node_modules node_modules_prod %{buildroot}%{nodejs_sitelib}/%{npm_name}
...
%check
%{__nodejs} -e 'require("./")'
# Setup bundled dev node_modules for testing
# Note: this cannot be in %%prep or the dev node_modules
# can get pulled into the regular rpm
tar xfz %{SOURCE2}
pushd node_modules
ln -s ../node_modules_dev/* .
popd
pushd node_modules/.bin
ln -s ../../node_modules_dev/.bin/* .
popd
# Example test run using the binary in ./node_modules/.bin/
./node_modules/.bin/vows --spec --isolate
...
Installing Modules

Loading…

User avatar None

String added in the repository
License: <license1> AND <license2> AND <license3>
...
Source3: %{npm_name}-%{version}-bundled-licenses.txt
...
%prep
...
cp %{SOURCE3} .
...
%files
%license LICENSE %{npm_name}-%{version}-bundled-licenses.txt
License: <license1> AND <license2> AND <license3>
...
Source3: %{npm_name}-%{version}-bundled-licenses.txt
...
%prep
...
cp %{SOURCE3} .
...
%files
%license LICENSE %{npm_name}-%{version}-bundled-licenses.txt
3 months ago
Browse all string changes

Things to check

Ellipsis

The string uses three dots (...) instead of an ellipsis character (…)

Reset

Glossary

English English
No related strings found in the glossary.

18592278 String information

Source string description
type: delimited block .
Flags
no-wrap, read-only
Source string location
./pages/Node.js.adoc:96
String age
3 months ago
Last updated
3 months ago
Source string age
3 months ago
Translation file
pot/master/pages/Node.js.pot, string 30