[WIP] Update Node.js guidelines, replacing nodejs-packaging-bundler with npm2rpm #1553
No reviewers
Labels
No labels
announce
bootstrap
Closed As
accepted
Closed As
duplicate
Closed As
exceptionexpired
Closed As
fixed
Closed As
invalid
Closed As
nothingtodo
Closed As
permanentexception
Closed As
rejected
Closed As
temporaryexception
Closed As
wontfix
cmake
committee
draftneeded
hasdraft
meeting
meson
needinfo
Priority
In Committee
Priority
Needs Review
Priority
Waiting For Reporter
rust
writeup
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
packaging/guidelines!1553
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "gordonmessmer/guidelines:nodejs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This change describes a change of tools that I will discuss with the Node.js SIG.
WIP Update Node.js guidelines, replacing nodejs-packaging-bundler with npm2rpmto [WIP] Update Node.js guidelines, replacing nodejs-packaging-bundler with npm2rpm@ -311,4 +257,0 @@URL: https://github.com/substack/tapeSource0: https://registry.npmjs.org/%{npm_name}/-/%{npm_name}-%{version}.tgzSource1: %{npm_name}-%{version}-nm-prod.tgzSource2: %{npm_name}-%{version}-nm-dev.tgzRunning test suite is important IMHO. Why is the example removed?
@ -367,2 +312,3 @@./node_modules/.bin/tap test/*.js%cleanrm -rf %{buildroot} %{npm_cache_dir}Is this required? Isn't the
%cleansection discouraged these days?db8355d0dbto7668baadbcThanks for taking a look. I cleaned up the spec example a little bit.
Is this ready for FPC to take a final look at and merge? If so can you remove the WIP prefix?
No, not ready yet. This change illustrates what the guidelines might look like if Fedora adopted npm2rpm instead of its current tooling. Before this can be merged, the Node.JS SIG really needs to evaluate that tool, and work with the upstream project to determine whether they'd carry changes that it would require to be suitable for Fedora.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.