Bug 261336 - www/node: shouldn't this point to LTS version?
Summary: www/node: shouldn't this point to LTS version?
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-19 15:32 UTC by bgdnlp
Modified: 2022-11-07 14:46 UTC (History)
0 users

See Also:
bugzilla: maintainer-feedback? (bhughes)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description bgdnlp 2022-01-19 15:32:02 UTC 
Run `pkg install node`, it will install node17 (no npm). Now run `pkg install npm`. It uninstalls node17 and install npm and node16.

I might be wrong, but I would expect www/node and www/npm (no version) to install the same versions.

As far as I can tell the problem is that "npm" is set to depend on "node" (no version), but the default node version in bsd.default-versions.mk is set to LTS:

NODEJS_DEFAULT?=    lts

which right now results in the conflict described. If it's considered a conflict. I know I can edit the defaults, I'm talking about the packages that pkgng installs.

So the question actually is, shouldn't www/node and the build defaults point to the same node version?
Comment 1 Rene Ladan freebsd_committer freebsd_triage 2022-11-07 14:46:42 UTC 
Maintainer reset.