Without having any default stream, this generator has to be
stream-specific; therefore it is now being shipped by nodejs*-devel
for each stream.
Related: RHEL-67814
It is out of date as of
https://www.fedoraproject.org/wiki/Changes/NodejsRepackaging and we now
have packaging instructions included in the README.md of the individual
Node.js interpreter packaging repositories.
Signed-off-by: Stephen Gallagher <sgallagh@redhat.com>
The previous behaviour assumed that in a bundled package path,
there is always `node_modules` directory on each other spot – i.e.:
npm/node_modules/<dep1>/node_modules/<subdep>
^ ^
With namespaced bundled packages, this is no longer necessary the truth:
npm/node_modules/@nmcli/<dep1>/node_modules/…
^ ! – expected node_modules
---
The previous implementation considered any directory not named
`node_modules` as a package directory, and tried to process it as such.
Among other things, it pruned the list of subdirectories to be processed
to just another `node_modules` subdir, if that existed.
With namespaced packages, this pruning in essence happened too soon,
and so they were skipped altogether.
With this patch applied, only directories that directly contain
the `package.json` file are processed as package directories,
meaning that the walk should correctly descend into namespaces
(even nested ones, if they appear).
Resolves: rhbz#2029904
bundler: Handle archaic license metadata
bundler: Warn about bundled dependencies with no license metadata
Signed-off-by: Stephen Gallagher <sgallagh@redhat.com>
Adds support for archaic forms of the license metadata in
package.json where the license field is an object rather than a
string.
Also removes the need to post-process the 'null' entries.
Resolves: rhbz#1920206
Signed-off-by: Stephen Gallagher <sgallagh@redhat.com>
Add nodejs-packaging-bundler subpackage in spec file
Update README.md with comments about nodejs-packaging-bundler
and an example spec file that uses bundling
Signed-off-by: Troy Dawson <tdawson@redhat.com>
Since the scripts and tools in this package are really Fedora
(and derivatives) specific, it doesn't really make a lot of
sense to maintain them in a separate upstream with tarball
releases.
This moves all the files into dist-git and builds the RPM from
there.
Signed-off-by: Stephen Gallagher <sgallagh@redhat.com>
This is no longer needed (Fedora and EPEL are both well past 0.10
at this point). It was also incorrect to begin with. It should have
been `Conflicts: nodejs(engine) < 0.10.13` since it was only intended
to force the upgrade if it was currently installed, not to force
nodejs itself to be brought in.
Signed-off-by: Stephen Gallagher <sgallagh@redhat.com>
