Re: [Pkg-javascript-devel] Javascript policy and npm2deb
Quoting Pirate Praveen (2017-10-12 08:25:06) > On ബുധന് 11 ഒക്ടോബര് 2017 10:10 വൈകു, Ben Finney wrote: > > What change to the policy do you suggest? > > > Add this, > > 6. If the library is primarily developed as a Node.js module and browser > part is generated from Node.js sources using a module bundler like > browserify, webpack or rollup, it should follow > https://wiki.debian.org/Javascript/Nodejs/Manual I see no need for making policy on such detail. Seems the need for such policy is to keep code in npm2deb simple, but If only a "should" then npm2den needs to handle exceptions anyway. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Javascript policy and npm2deb
On ബുധന് 11 ഒക്ടോബര് 2017 10:10 വൈകു, Ben Finney wrote: > What change to the policy do you suggest? > Add this, 6. If the library is primarily developed as a Node.js module and browser part is generated from Node.js sources using a module bundler like browserify, webpack or rollup, it should follow https://wiki.debian.org/Javascript/Nodejs/Manual signature.asc Description: OpenPGP digital signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Javascript policy and npm2deb
On Wed, 11 Oct 2017 16:19:30 +0530, Pirate Praveensaid: > Hi, In a recent bug report, I came across this disparity, > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877213#36 > npm2deb creates source packages with node- prefix. I think the policy > should be updated to reflect this. Yup. https://wiki.debian.org/Javascript/Nodejs/Manual says that the source package should be called "node-", which is clearly a conflict with what https://wiki.debian.org/Javascript/Policy says. It becomes even more silly when you have a source package that happens to build, say, a Node library, a Python module, and a C library, since you may end up with a Python package whose source package is named "node-something". (In fact, if emscripten ever becomes usable in Debian again, I have one source package that could potentially produce binary packages for JavaScript, NodeJS, Java, Python, Objective-C, and C. It would be fun if the Python and Java policies also told me how to name the source package.) IMHO, the policies should not mandate a source package name, which is partially why I omitted it from my proposed JavaScript policy (https://wiki.debian.org/HubertChathi/JavaScriptPolicy -- which I still need to update). It might be fine to *suggest* a name, but I don't think it should be a "should"/"recommend" (at least not in the sense that those words are used in the Debian Policy Manual). My preference would be to completely remove those clauses from the policies, but at the very least, the node and JavaScript policies should be made consistent. -- Hubert Chathi -- https://www.uhoreg.ca/ Jabber: hub...@uhoreg.ca -- Matrix: @uhoreg:matrix.org PGP/GnuPG key: 4096R/F24C F749 6C73 DDB8 DCB8 72DE B2DE 88D3 113A 1368 -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Javascript policy and npm2deb
Pirate Praveenwrites: > In a recent bug report, I came across this disparity, > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877213#36 > > npm2deb creates source packages with node- prefix. I think the policy > should be updated to reflect this. What change to the policy do you suggest? -- \ “Skepticism is the highest duty and blind faith the one | `\ unpardonable sin.” —Thomas Henry Huxley, _Essays on | _o__) Controversial Questions_, 1889 | Ben Finney -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Javascript policy and npm2deb
Please CC me on all replies, I don't receive mail from this mailing list due to too much node-related traffic that I don't want to see. > In a recent bug report, I came across this disparity, > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877213#36 > > npm2deb creates source packages with node- prefix. I think the policy > should be updated to reflect this. As I mentioned on that bug report, not all javascript is node or npm. It would be totally inappropriate to rename jquery or mathjax as node-jquery or node-mathjax. My d3-format source package provides both node-d3-format and libjs-d3-format, which is a standalone javascript library that doesn't need node at all. The build does not need NPM, and it needs nodejs only to run uglifyjs. Calling a package node-XXX just because a build tool uses /usr/bin/nodejs is ridiculous, we might as well rename all/most packages to cc-XXX or gcc-XXX. More generally we should be liberating as many Debian javascript packages as possible from the shackles of the neoliberal "free-market" npm "ecosystem". X -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Javascript policy and npm2deb
Hi, In a recent bug report, I came across this disparity, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877213#36 npm2deb creates source packages with node- prefix. I think the policy should be updated to reflect this. Thanks Praveen signature.asc Description: OpenPGP digital signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel