Re: [Bug 2075170] New: Review Request: npm - A JavaScript Package Manager
On Wed, Apr 27, 2022 at 10:26 AM Neal Gompa wrote: > > On Wed, Apr 27, 2022 at 10:19 AM Stephen Gallagher > wrote: > > > > On Wed, Apr 13, 2022 at 2:39 PM Stephen Gallagher > > wrote: > > > > > > I've just submitted a review request for separating out NPM into its > > > own package (again). This is being done for a couple reasons: > > > > > > 1) To get rid of the ridiculous release field and take advantage of > > > the %autorelease macro > > > 2) I'm planning to rework how the nodejs packages work to make > > > different versions parallel-installable (with the alternatives > > > infrastructure owning /usr/bin/node). I want to keep NPM in a common > > > location (/usr/lib/node_modules) so that it will work with whatever > > > Node is in use. > > > > I completely missed the most important reason: > > 3) EPEL 9 has announced that it will not support modules, so I want > > there to be some way (aside from the official RHEL releases) to get > > Node.js packages there. > > EPEL has said it *can't* support modules, not that it *won't*. There > is a very important distinction here. Sorry, I was using "won't" in the sense of future tense, not in the sense of willingness. > Because the Module Build System > cannot build modules on top of remote modules, there's no way to > reliably and correctly produce modular content for EPEL on top of > modular RHEL content. > > Starting with Koji 1.28, it's possible to configure build tags to > enable modules: https://pagure.io/koji/issue/2483 > > However, MBS still lacks the ability to use this capability: > https://pagure.io/fm-orchestrator/issue/1653 > > Fix that, and EPEL can build layered modules. I believe it was more than that, though. It was also a matter of capacity. I've CCed Troy Dawson to speak more to that. I don't have the details handy. ___ nodejs mailing list -- nodejs@lists.fedoraproject.org To unsubscribe send an email to nodejs-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/nodejs@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [Bug 2075170] New: Review Request: npm - A JavaScript Package Manager
On Wed, Apr 27, 2022 at 10:19 AM Stephen Gallagher wrote: > > On Wed, Apr 13, 2022 at 2:39 PM Stephen Gallagher wrote: > > > > I've just submitted a review request for separating out NPM into its > > own package (again). This is being done for a couple reasons: > > > > 1) To get rid of the ridiculous release field and take advantage of > > the %autorelease macro > > 2) I'm planning to rework how the nodejs packages work to make > > different versions parallel-installable (with the alternatives > > infrastructure owning /usr/bin/node). I want to keep NPM in a common > > location (/usr/lib/node_modules) so that it will work with whatever > > Node is in use. > > I completely missed the most important reason: > 3) EPEL 9 has announced that it will not support modules, so I want > there to be some way (aside from the official RHEL releases) to get > Node.js packages there. EPEL has said it *can't* support modules, not that it *won't*. There is a very important distinction here. Because the Module Build System cannot build modules on top of remote modules, there's no way to reliably and correctly produce modular content for EPEL on top of modular RHEL content. Starting with Koji 1.28, it's possible to configure build tags to enable modules: https://pagure.io/koji/issue/2483 However, MBS still lacks the ability to use this capability: https://pagure.io/fm-orchestrator/issue/1653 Fix that, and EPEL can build layered modules. -- 真実はいつも一つ！/ Always, there's only one truth! ___ nodejs mailing list -- nodejs@lists.fedoraproject.org To unsubscribe send an email to nodejs-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/nodejs@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [Bug 2075170] New: Review Request: npm - A JavaScript Package Manager
On Wed, Apr 13, 2022 at 2:39 PM Stephen Gallagher wrote: > > I've just submitted a review request for separating out NPM into its > own package (again). This is being done for a couple reasons: > > 1) To get rid of the ridiculous release field and take advantage of > the %autorelease macro > 2) I'm planning to rework how the nodejs packages work to make > different versions parallel-installable (with the alternatives > infrastructure owning /usr/bin/node). I want to keep NPM in a common > location (/usr/lib/node_modules) so that it will work with whatever > Node is in use. I completely missed the most important reason: 3) EPEL 9 has announced that it will not support modules, so I want there to be some way (aside from the official RHEL releases) to get Node.js packages there. ___ nodejs mailing list -- nodejs@lists.fedoraproject.org To unsubscribe send an email to nodejs-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/nodejs@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [Bug 2075170] New: Review Request: npm - A JavaScript Package Manager
On Thu, Apr 14, 2022 at 5:43 AM Zuzana Svetlikova wrote: > > Hi. > > I see your point, but is this really *needed*? > Has anyone ever complained about ugly release field, or is this just a > cosmetic thing? I've heard complaints, but that aspect *is* mostly cosmetic. By doing this, I'll also be able to switch to %autorelease for both Node.js and NPM, which is a benefit to packaging simplicity (and makes merge requests to dist-git less prone to needing a rebase). > Does npm being a separate package or being part of nodejs matter when it > comes to npm modules parallel-instalable? Yes, because it allows us to keep a single version of NPM irrespective of the version of Node.js being used. (Current NPM releases support Node.js 12+, which is the same set of versions we support). As for Node.js, I'm actually going to end up de-modularizing it in Fedora. I've figured out how to make it work so that Node.js can be made parallel-installable as nodejs12, nodejs14, nodejs16, etc. packages (with an appropriate one providing the default `/usr/bin/node` for each release). > Won't this cause discrepancies and give us more work when it comes to > updates? I believe that was one of the main reasons why we merged npm into > nodejs. No, the main reason we merged npm into nodejs was because it predated the current bundling policy for Fedora and Node.js had an exception granted for it. It was too hard to keep NPM up to date back then because we were packaging all of its dependencies individually (and they were generally not compatible with other packages in the distro). Now that we have the current bundling policy, we are free to maintain it separately. In the general case, I plan to ship whatever version is shipped with the latest stable release of Node.js. The only reason I am packaging 8.6.0 in this request is because I can only drop the release field nonsense during a version number increase (otherwise it breaks the update path). In future updates, I'll track whatever version is most compatible with the supported stable versions of Node.js. (For example, when 18.0.0 releases next week, if it's carrying an NPM package that has dropped support for Node.js 12, I'll wait to package that version until Node.js 12.x goes EOL on the 30th unless a CVE forces my hand.) > Also, do you plan on shipping npm as a dnf module or rpm? RPM, not module. The same will also become true of the existing Node.js modules: they'll be converted to non-modular packages. ___ nodejs mailing list -- nodejs@lists.fedoraproject.org To unsubscribe send an email to nodejs-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/nodejs@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [Bug 2075170] New: Review Request: npm - A JavaScript Package Manager
Hi. I see your point, but is this really *needed*? Has anyone ever complained about ugly release field, or is this just a cosmetic thing? Does npm being a separate package or being part of nodejs matter when it comes to npm modules parallel-instalable? Won't this cause discrepancies and give us more work when it comes to updates? I believe that was one of the main reasons why we merged npm into nodejs. Also, do you plan on shipping npm as a dnf module or rpm? Zuzka On Wed, Apr 13, 2022 at 10:22 PM Neal Gompa wrote: > On Wed, Apr 13, 2022 at 2:40 PM Stephen Gallagher > wrote: > > > > I've just submitted a review request for separating out NPM into its > > own package (again). This is being done for a couple reasons: > > > > 1) To get rid of the ridiculous release field and take advantage of > > the %autorelease macro > > 2) I'm planning to rework how the nodejs packages work to make > > different versions parallel-installable (with the alternatives > > infrastructure owning /usr/bin/node). I want to keep NPM in a common > > location (/usr/lib/node_modules) so that it will work with whatever > > Node is in use. > > > > If someone on this list would be willing to perform the package > > review, I'd be appreciative. > > > > I grabbed it. > > > > -- > 真実はいつも一つ！/ Always, there's only one truth! > ___ > nodejs mailing list -- nodejs@lists.fedoraproject.org > To unsubscribe send an email to nodejs-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/nodejs@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ nodejs mailing list -- nodejs@lists.fedoraproject.org To unsubscribe send an email to nodejs-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/nodejs@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [Bug 2075170] New: Review Request: npm - A JavaScript Package Manager
On Wed, Apr 13, 2022 at 2:40 PM Stephen Gallagher wrote: > > I've just submitted a review request for separating out NPM into its > own package (again). This is being done for a couple reasons: > > 1) To get rid of the ridiculous release field and take advantage of > the %autorelease macro > 2) I'm planning to rework how the nodejs packages work to make > different versions parallel-installable (with the alternatives > infrastructure owning /usr/bin/node). I want to keep NPM in a common > location (/usr/lib/node_modules) so that it will work with whatever > Node is in use. > > If someone on this list would be willing to perform the package > review, I'd be appreciative. > I grabbed it. -- 真実はいつも一つ！/ Always, there's only one truth! ___ nodejs mailing list -- nodejs@lists.fedoraproject.org To unsubscribe send an email to nodejs-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/nodejs@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fwd: [Bug 2075170] New: Review Request: npm - A JavaScript Package Manager
I've just submitted a review request for separating out NPM into its own package (again). This is being done for a couple reasons: 1) To get rid of the ridiculous release field and take advantage of the %autorelease macro 2) I'm planning to rework how the nodejs packages work to make different versions parallel-installable (with the alternatives infrastructure owning /usr/bin/node). I want to keep NPM in a common location (/usr/lib/node_modules) so that it will work with whatever Node is in use. If someone on this list would be willing to perform the package review, I'd be appreciative. -- Forwarded message - From: Date: Wed, Apr 13, 2022 at 2:27 PM Subject: [Bug 2075170] New: Review Request: npm - A JavaScript Package Manager To: https://bugzilla.redhat.com/show_bug.cgi?id=2075170 Bug ID: 2075170 Summary: Review Request: npm - A JavaScript Package Manager Product: Fedora Version: rawhide Hardware: All OS: Linux Status: NEW Component: Package Review Severity: medium Priority: medium Assignee: nob...@fedoraproject.org Reporter: sgall...@redhat.com QA Contact: extras...@fedoraproject.org CC: package-rev...@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Spec URL: https://copr-dist-git.fedorainfracloud.org/cgit/sgallagh/npm/npm.git/plain/npm.spec SRPM URL: https://download.copr.fedorainfracloud.org/results/sgallagh/npm/srpm-builds/04217393/npm-8.6.0-1.fc37.src.rpm Description: npm is the world's largest software registry. Open source developers from every continent use npm to share and borrow packages, and many organizations use npm to manage private development as well. npm consists of three distinct components: * the website * the Command Line Interface (CLI) * the registry Use the [*website*](https://npmjs.com) to discover packages, set up profiles, and manage other aspects of your npm experience. For example, you can set up [organizations](https://www.npmjs.com/features) to manage access to public or private packages. The [*CLI*](https://docs.npmjs.com/cli/npm) runs from a terminal, and is how most developers interact with npm. The [*registry*](https://docs.npmjs.com/misc/registry) is a large public database of JavaScript software and the meta-information surrounding it. ## Use npm to . . . * Adapt packages of code for your apps, or incorporate packages as they are. * Download standalone tools you can use right away. * Run packages without downloading using [npx](https://www.npmjs.com/package/npx). * Share code with any npm user, anywhere. * Restrict code to specific developers. * Create organizations to coordinate package maintenance, coding, and developers. * Form virtual teams by using organizations. * Manage multiple versions of code and code dependencies. * Update applications easily when underlying code is updated. * Discover multiple ways to solve the same puzzle. * Find other developers who are working on similar problems and projects. Fedora Account System Username: sgallagh -- You are receiving this mail because: You reported the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2075170 ___ nodejs mailing list -- nodejs@lists.fedoraproject.org To unsubscribe send an email to nodejs-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/nodejs@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Review request
Could somebody have a look at reviewing 1274512 please, only I just accidentally pushed a nodejs-tape update that requires it... Tom -- Tom Hughes (t...@compton.nu) http://compton.nu/ ___ nodejs mailing list nodejs@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/nodejs@lists.fedoraproject.org
