- Moved text around a bit to be hopefully more readable
- Add few paragraphs on handling runtime dependencies
- Fixed typos and stylistic errors

@@ -16,3 +16,3 @@
 * The name of a Node.js extension/library package must start with _nodejs-_ then the upstream name or name used in the npm registry. For example: _nodejs-foomodule_. While it is uncommon for a package's name to contain _node_, if it does, you should still add the nodejs prefix. For instance, the npm registry contains a _uuid_ and a _node-uuid_ module, which would need to be named _nodejs-uuid_ and _nodejs-node-uuid_, respectively.
 
-== BuildRequires
+== Managing versioned stream dependencies

@@ -19,0 +18,4 @@
+== Managing versioned stream dependencies
+
+In Fedora, multiple Node.js versions are generally available at any given time.
+You should take that into an account when specifying dependencies for your package.

@@ -19,0 +20,4 @@
+In Fedora, multiple Node.js versions are generally available at any given time.
+You should take that into an account when specifying dependencies for your package.
+
+If your package could be used with any currently supported major version of Node.js,

@@ -19,0 +21,4 @@
+You should take that into an account when specifying dependencies for your package.
+
+If your package could be used with any currently supported major version of Node.js,
+it is recommended to use the generic `+nodejs+` package and/or it's subpackages.

@@ -19,0 +22,4 @@
+
+If your package could be used with any currently supported major version of Node.js,
+it is recommended to use the generic `+nodejs+` package and/or it's subpackages.
+This will provide one of the supported major versions;

@@ -19,0 +23,4 @@
+If your package could be used with any currently supported major version of Node.js,
+it is recommended to use the generic `+nodejs+` package and/or it's subpackages.
+This will provide one of the supported major versions;
+however, the exact version might be different in different Fedora versions.

@@ -19,0 +25,4 @@
+This will provide one of the supported major versions;
+however, the exact version might be different in different Fedora versions.
+
+If you know that your package will only work with a subset of the currently supported Node.js versions (or even a single one),

@@ -19,0 +26,4 @@
+however, the exact version might be different in different Fedora versions.
+
+If you know that your package will only work with a subset of the currently supported Node.js versions (or even a single one),
+you should pick one of them and request it specifically.

@@ -23,6 +37,22 @@ To build a package that is a nodejs module, bundles or uses nodejs modules, or n
 BuildRequires: nodejs-devel
 ....
 
+If the package only builds against specific version(s) of Node.js, request the specific version:

@@ -26,0 +47,4 @@
+For example:
+
+....
+$ sudo dnf --repo=rawhide repoquery --whatprovides 'alternative-for(nodejs-devel)'

@@ -19,0 +44,4 @@
+
+If you know that your package will only work with a subset of the currently supported Node.js versions (or even a single one),
+you should pick one of them and require it specifically.
+Use the `+nodejs{XY}+` package (e.g. `+nodejs24+` for Node.js v24.x.y) for this.

@@ -23,6 +54,39 @@ To build a package that is a nodejs module, bundles or uses nodejs modules, or n
 BuildRequires: nodejs-devel
 ....
 
+If the package only builds against a specific version of Node.js, BuildRequire it explicitly.

@@ -26,0 +71,4 @@
+
+....
+# This package requires /usr/bin/node to launch Node.js v24.x or any newer
+Requires: alternative-for(nodejs-bin) >= 24