Re: NodeJS with NPM

[Greg Troxel <gdt%lexort.com@localhost>]

Adam <adam%netbsd.org@localhost> writes:

> Because lang/npm is quite problematic to build and update (requires
> internet connection to pull the dependencies, and so on),

(I'm assuming is for post branch, as it seems a major change and not
comfortable with respect to "all problems on all platforms, even ones we
can't test on, are expected to be resolved by branch start".  I haven't
been seeing complaints from users about the current situation, so it
doesn't seem like an emergency.)

I don't object, but I would like to understand this better.

Can you explain the sitation with lang/npm?  It sounds like you are
saying it doesn't conform to pkgsrc rules of no net usage at build time.
I built it and didn't spot that, but I realize these things are sneaky.
If it isn't using the net at build time, I don't follow.

> I would like to remove the package and enable npm for all lang/node
> packages, as it is a default distribution option for NodeJS, and I
> think users expect NodeJS to come with npm.

Are you saying that if you build and install node following upstream
build instructions that you will get an npm executable?

Are the npm sources in the nodejs source tarballs?  Are they the same as
what lang/npm uses?

What do other packaging systems do?  (On a Debian system, I have nodejs
installed and no npm executable.  But I realize that there are split
packages.  On a Raspberry Pi OS system, with node from an alternate
repo, I do have /bin/npm.)

Why will whatever is problematic with building npm as a package not be
problematic when npm is built within the nodejs build?