* Stephen Gallagher:
On Wed, Sep 7, 2022 at 1:36 PM Ewoud Kohl van Wijngaarden
<ewoud+fedora(a)kohlvanwijngaarden.nl> wrote:
> But what if $package a.b only supports node 16 and $package x.y only
> supports node 20. Looking at /usr/lib/node_modules/npm/node_modules I
> don't see any version numbers in directories so they can't be
> coinstalled. Does it mean you drop the node 16 package once node 20 is
> packaged? It will still be in the load path for node 16 so it could
> accidentally load incompatible code.
So, some of this is going to be resolved by policy. Currently, our
official policy[1] on Node.js packages in Fedora allows packaging:
* The interpreter, development headers/libraries, and the assorted
tools to manage project-level installations. Examples: nodejs, npm,
yarn
* Packages that provide applications that users would want to use in
their shell. Examples: uglify
Note that we *expressly* do not list NPM "libraries". We only package
applications. Further down on the guidelines page you will see that
our packaging approach involves bundling the necessary dependencies
into the application. This is in line with Node.js's own
recommendations.
Ahh, this also explains why co-installable -devel packages are not
required in the buildroot.
Thanks,
Florian