Date: Sun, 26 Jan 2025 21:48:11 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 284373] www/npm: Maybe should be renamed? Message-ID: <bug-284373-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D284373 Bug ID: 284373 Summary: www/npm: Maybe should be renamed? Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: sunpoet@FreeBSD.org Reporter: bob@vesterman.com Flags: maintainer-feedback?(sunpoet@FreeBSD.org) Assignee: sunpoet@FreeBSD.org I don't know enough about this to really say this *should* be done (and eve= n if it should, I don't think it's a terribly pressing issue), but I think it sh= ould at least be considered by people who know more about it than me, if they haven't done so already: I recently decided to install node on one of my FreeBSD machines. So I took= to FreshPorts and searched for "node". That came up with a list that included: www/node www/node21 www/node22 www/node23 (and so forth) www/npm-node21 www/npm-node22 www/npm-node23 (and so forth) Based on that, my thoughts, in order, were: 1. OK, I want the www/node metaport. 2. Oh, looks like I have to explicitly install npm, too. 3. Wait, but there's no www/npm-node metaport? 4. So what if I choose some version of npm appropriate to the current www/n= ode, and then later the meaning of "www/node" changes? Sounds potentially danger= ous. 5. That's weird. Well, then I guess I'll instead figure out what www/node actually points to, then I'll just install the appropriate www/node* and www/npm-node*. I then did so, installing both www/node22 and www/npm-node22. Upon having d= one so, the package message for www/node22 suggested that if I want npm, I shou= ld install www/npm. At this point I'd like to be explicit about what I see as the issue: "www/n= pm" did not (and will not) show up on a (default settings) FreshPorts search for "node", nor would it show up when directly searching for "node" within /usr/ports/www via ls or find or whatever... but "npm-node<version>" did and will. Again, I don't know that this should be changed, and even if it should I th= ink it's only a very minor issue, but... maybe changing the name of www/npm to www/npm-node might save someone in the future a little hassle, as it would = have done for me. --=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-284373-7788>