[Pkg-javascript-devel] Bug#622628: Bug#622628: Bug#622628: npm no longer works
On 12-03-08 at 10:34am, Felipe Sateler wrote: > On Tue, Mar 6, 2012 at 13:42, Jonas Smedegaard wrote: > > On 12-03-06 at 01:14pm, Felipe Sateler wrote: > >> npm is too old to function with current nodejs in debian. Please > >> update the package! > >> > >> I might (hopefully...) have time to help, and I will need this. Is > >> there any roadmap on what is missing to get an updated npm package? > > > > Great! > > > > Pull the git and see the notes in changelog about what's missing. > > One of the important parts is to replace the node_modules by a package > of their own. > I propose to do otherwise, and just include them. When the modules get > packaged on their own, strip them from npm. > > > BTW, npm upstream is now distributed as part of node.js. Does it make > sense to split it? IMO, it makes more sense to distribute it as > upstream, this should eliminate the incompatibilities we see in the > current npm package with current nodejs. Is it now maintained by same upstream author, using same release schedule as Node itself? Or does it still have a separate project home and is just includes as a convencience copy with Node? If the latter, I strongly recommend to maintain it as a separate project. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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
[Pkg-javascript-devel] Bug#622628: Bug#622628: Bug#622628: npm no longer works
On 06/03/2012 18:06, Jonas Smedegaard wrote: > On 12-03-06 at 05:40pm, Jérémy Lal wrote: >> On 06/03/2012 17:14, Felipe Sateler wrote: >>> I might (hopefully...) have time to help, and I will need this. Is >>> there any roadmap on what is missing to get an updated npm package? >> >> There is : >> >> * package dependencies that are in node_modules >> * make sure the license is free (MIT +no-false-attribs) >> >> I update regularly the collab-maint git repository, and >> npm 1.1.4 package built from it is usable. > > Related to that: Please don't update in git the copyright_hints file if > changes not reflected in copyirhgt file. The very point of that hints > file is to track changes. In the case of npm, i intended to ignore changes in ./node_modules since what's inside must be either reviewed or excluded from tarball. I usually check all new files, and differences, manually. I am not perfect at this, though. > Also, please do not blindly bump format hint in first line of copyright > file. License field is not allowed to contain spaces in final release > of the format. Lintian warnings about copyright format let me naively think the syntax was strictly checked... > Oh, and that fork or Expat license seems to have a flaw: It is not clear > whether it talks only about the original author or any subsequent > author. I would recommend upstream to not try hack legalese but instead > simply document clearly a friendly _request_ to do do same as now > codified in license. I will forward that remark and recommandation to Isaac. He's hard to convince for now. Jérémy. ___ 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] Bug#622628: Bug#622628: Bug#622628: npm no longer works
On 12-03-06 at 05:40pm, Jérémy Lal wrote: > On 06/03/2012 17:14, Felipe Sateler wrote: > > I might (hopefully...) have time to help, and I will need this. Is > > there any roadmap on what is missing to get an updated npm package? > > There is : > > * package dependencies that are in node_modules > * make sure the license is free (MIT +no-false-attribs) > > I update regularly the collab-maint git repository, and > npm 1.1.4 package built from it is usable. Related to that: Please don't update in git the copyright_hints file if changes not reflected in copyirhgt file. The very point of that hints file is to track changes. Also, please do not blindly bump format hint in first line of copyright file. License field is not allowed to contain spaces in final release of the format. Oh, and that fork or Expat license seems to have a flaw: It is not clear whether it talks only about the original author or any subsequent author. I would recommend upstream to not try hack legalese but instead simply document clearly a friendly _request_ to do do same as now codified in license. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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
