Bug#794890: [Pkg-javascript-devel] Bug#794890: npm: new upstream version

2016-11-24 Thread Joerg Jaspert
On 14501 March 1977, Jérémy Lal wrote: >> - If upstream deicdes to remove one of the bundled libs, which you have >>a provides for - and that provides is used in debian (has rdepends), >>you just earned a new package to maintain. > Unless no other package depends on it ? Yeah sure, thats

Bug#794890: [Pkg-javascript-devel] Bug#794890: npm: new upstream version

2016-11-24 Thread Jérémy Lal
2016-11-24 9:12 GMT+01:00 Joerg Jaspert : > On 14501 March 1977, Jérémy Lal wrote: >>> - This is not a blanket for having embedded code copies all over the >>>place. >>>So yes, this should Provide: all those submodules and make them >>>usable by whoever depends on it. > >>> - This mus

Bug#794890: [Pkg-javascript-devel] Bug#794890: npm: new upstream version

2016-11-24 Thread Joerg Jaspert
On 14501 March 1977, Jérémy Lal wrote: >> - This is not a blanket for having embedded code copies all over the >>place. >>So yes, this should Provide: all those submodules and make them >>usable by whoever depends on it. >> - This must be rebuildable in Debian. That is, the package s

Bug#794890: [Pkg-javascript-devel] Bug#794890: npm: new upstream version

2016-11-23 Thread Jérémy Lal
2016-11-24 0:42 GMT+01:00 Joerg Jaspert : > On 14500 March 1977, Michael Prokop wrote: > >>> > Overall, I'm not sure we are providing our users something good with >>> > the current situation. Though what realistic options do we have get >>> > forward here? Any thoughts? > > It neither helps Users

Bug#794890: [Pkg-javascript-devel] Bug#794890: npm: new upstream version

2016-11-23 Thread Joerg Jaspert
On 14500 March 1977, Michael Prokop wrote: >> > Overall, I'm not sure we are providing our users something good with >> > the current situation. Though what realistic options do we have get >> > forward here? Any thoughts? It neither helps Users nor Debian. >> Most, if not all, npm dependencies

Bug#794890: [Pkg-javascript-devel] Bug#794890: npm: new upstream version

2016-11-23 Thread Michael Prokop
Cc-ing ftpmas...@debian.org hereby with a (nearly) fullquote below - it's about #794890 and the situation of the npm package within Debian, we'd appreciate your input/feedback on this matter. Thanks! regards, -mika- * Jérémy Lal [Wed Nov 23, 2016 at 02:42:23PM +0100]: > 2016-11-23 14:18 GMT+01:00

Bug#794890: [Pkg-javascript-devel] Bug#794890: npm: new upstream version

2016-11-23 Thread Paolo Greppi
OK whereas if you have no locally installed soso, it will pick the system node-soso. I don't know much of the ruby world. But that looks like the same as you get in python, when you pass the --system-site-packages option to virtualenv. By default virtualenv is completely isolated from the global

Bug#794890: [Pkg-javascript-devel] Bug#794890: npm: new upstream version

2016-11-23 Thread Jérémy Lal
2016-11-23 15:45 GMT+01:00 Paolo Greppi : > On 23/11/2016 14:57, Jonas Smedegaard wrote: >> Npm is an *alternative* to using Debian packaged nodejs code. >> >> Users of Debian cannot tell anything about how same or similar tasks >> could be solved using Debian, because they evidently stopped trying

Bug#794890: [Pkg-javascript-devel] Bug#794890: npm: new upstream version

2016-11-23 Thread Paolo Greppi
Jonas, I beg to slightly differ on the point below. I think of npm or yarn/yarnpkg as the equivalent for the nodejs ecosystem of python virtualenv. There are workflows where you'd want to maintain a certain configuration of a webapp, phonegap app or website using a local set of modules / pinned v

Bug#794890: [Pkg-javascript-devel] Bug#794890: npm: new upstream version

2016-11-23 Thread Michael Prokop
* Jérémy Lal [Wed Nov 23, 2016 at 02:42:23PM +0100]: > 2016-11-23 14:18 GMT+01:00 Michael Prokop : [...] > > Looking at e.g. the current state of the node-request > > dependency (~2.78.0): > > % rmadison node-request > > node-request | 2.26.1-1 | stable | source, all > > node-reques

Bug#794890: [Pkg-javascript-devel] Bug#794890: npm: new upstream version

2016-11-23 Thread Jérémy Lal
Thank you for tackling the issue. See my answer below. 2016-11-23 14:18 GMT+01:00 Michael Prokop : > Disclaimer: I'm not blaming nor pointing to anyone, but I feel like > that this is yet again the team pattern and I'd really like to see > whether we have any way out of this... > > * Jérémy Lal [T

Bug#794890: [Pkg-javascript-devel] Bug#794890: npm: new upstream version

2016-11-23 Thread Michael Prokop
Disclaimer: I'm not blaming nor pointing to anyone, but I feel like that this is yet again the team pattern and I'd really like to see whether we have any way out of this... * Jérémy Lal [Tue Nov 15, 2016 at 11:27:02PM +0100]: > > Is really no one from the Debian Javascript Maintainers working on

Bug#794890: [Pkg-javascript-devel] Bug#794890: npm: new upstream version

2016-11-15 Thread Jérémy Lal
> Is really no one from the Debian Javascript Maintainers working on > the npm packaging or interested in having an up2date version > available for stretch? Are there any known blockers? Besides "takes a lot of time", no. The amount of work needed to complete that task is simply discouraging :( He