On 19.05.2017 12:15, Jérémy Lal wrote:
> 2017-05-19 12:07 GMT+02:00 Riku Voipio
>
> > Are there any complications to building npm as part of nodejs package?
I wouldn't do that - instead have separate packages:
(patches already sent upstream)
https://github.com/metux/nodejs
On Fri, May 19, 2017 at 12:15:32PM +0200, Jérémy Lal wrote:
> 2017-05-19 12:07 GMT+02:00 Riku Voipio :
>
> > Jérémy Lal:
> > > To others, preoccupied that npm won't be available in debian:
> > > - please help with npm maintenance
> > > - hopefully we'll make an updated version
2017-05-19 12:07 GMT+02:00 Riku Voipio :
> Jérémy Lal:
> > To others, preoccupied that npm won't be available in debian:
> > - please help with npm maintenance
> > - hopefully we'll make an updated version installable through debian
> backports
>
> Are there any complications
Jérémy Lal:
> To others, preoccupied that npm won't be available in debian:
> - please help with npm maintenance
> - hopefully we'll make an updated version installable through debian backports
Are there any complications to building npm as part of nodejs package?
Riku
--
Pkg-javascript-devel
Control: severity -1 grave
Contraol: tags -1 stretch sid
On Fri, Mar 17, 2017 at 12:50:11AM +0100, Jérémy Lal wrote:
>...
> I should have done this long before, but npm should not stay in testing:
> - `npm install thisorthatmodule` is failing for a growing list of modules
> - npmjs.org might drop
I actually did give a use case for this: try installing polymer as per the
instruction given on my initial report. It just doesn't work, as Jeremy
states. NPM is a growing, dynamic repository and you'll be hard pressed to
find any major package that is 3 years old and 100% compatible with the
2017-03-17 0:30 GMT+01:00 Ben Finney :
> Control: tags -1 + moreinfo
>
> Alex Henry wrote:
>> Severity: grave
>> Justification: renders package unusable
>
> Thank you for considering the severity of bug reports. You claim the
> package is unusable in general,