Date: Wed, 19 Jan 2022 15:32:02 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 261336] www/node: shouldn't this point to LTS version? Message-ID: <bug-261336-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D261336 Bug ID: 261336 Summary: www/node: shouldn't this point to LTS version? Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: bhughes@freebsd.org Reporter: freebsd.org@neant.ro Assignee: bhughes@freebsd.org Flags: maintainer-feedback?(bhughes@freebsd.org) Run `pkg install node`, it will install node17 (no npm). Now run `pkg insta= ll 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?=3D 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 th= at pkgng installs. So the question actually is, shouldn't www/node and the build defaults poin= t to the same node version? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-261336-7788>