Hello, As the nodejs bundle libraries by default change proposal has worked it's way through the process, a question came up that I'd like others opinions on.
Some nodejs packages also provide javascript sub-packages. An example is nodejs-underscore, also provides the js-underscore package.
What is the difference between the nodejs- and js- packages? The nodejs packages provide "server side" libraries. They are in a place that only your local server will see these libraries. The js- packages provide "browser side" libraries. These are libraries that are expected to be served by the web server to the users browsers.
Our nodejs proposal is supposed to only get rid of the server side libraries. We (the Nodejs SIG) do not feel we should be messing with the browser side (javascript) libraries. So, what to do.
For those nodejs libraries, that also provide javascript sub-packages, and that do not fall under the "Packages that provide binaries that users would want to use in their shell" clause: - Remove the nodejs package, leaving only the js- sub-package.
So, for our example nodejs-underscore also provides js-underscore. We would change the spec file so that it would only build js-underscore.
Does that seem like a good thing to do? Troy
On Fri, Dec 18, 2020 at 11:02 AM Troy Dawson tdawson@redhat.com wrote:
Hello, As the nodejs bundle libraries by default change proposal has worked it's way through the process, a question came up that I'd like others opinions on.
Some nodejs packages also provide javascript sub-packages. An example is nodejs-underscore, also provides the js-underscore package.
What is the difference between the nodejs- and js- packages? The nodejs packages provide "server side" libraries. They are in a place that only your local server will see these libraries. The js- packages provide "browser side" libraries. These are libraries that are expected to be served by the web server to the users browsers.
Our nodejs proposal is supposed to only get rid of the server side libraries. We (the Nodejs SIG) do not feel we should be messing with the browser side (javascript) libraries. So, what to do.
For those nodejs libraries, that also provide javascript sub-packages, and that do not fall under the "Packages that provide binaries that users would want to use in their shell" clause:
- Remove the nodejs package, leaving only the js- sub-package.
So, for our example nodejs-underscore also provides js-underscore. We would change the spec file so that it would only build js-underscore.
Does that seem like a good thing to do?
I am fully in favor of this. We may also want to go through the Package Renaming process[1] to switch from calling the source packages nodejs-foo to js-foo. What are the opinions on that?
Full disclosure: I discussed this with Troy before he sent this email back in December. I'm replying now mostly to bump this discussion back into view.
[1] https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-repla...
nodejs@lists.fedoraproject.org
-
Stephen Gallagher -
Troy Dawson