Bug#745687: [Pkg-javascript-devel] Bug#745687: Bug#745687: new upstream version (2.x series)
Related to the point above, it's interesting to note that dryice is a good example of what we could ask upstream to merge back into source-map. I'll leave that to you too. I added an issue: https://github.com/mozilla/source-map/issues/108 let's see what happens. Jérémy. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745687: [Pkg-javascript-devel] Bug#745687: Bug#745687: new upstream version (2.x series)
Le jeudi 01 mai 2014 à 11:15 +0200, Jérémy Lal a écrit : Related to the point above, it's interesting to note that dryice is a good example of what we could ask upstream to merge back into source-map. I'll leave that to you too. I added an issue: https://github.com/mozilla/source-map/issues/108 I missed the fact that dryice is a devDependencies of projects that are well alive. Packaged it must be, then. Jérémy. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745687: [Pkg-javascript-devel] Bug#745687: Bug#745687: new upstream version (2.x series)
About node-source-map: It build-depends on dryice (=0.4.8). You can find a pre-release package in pkg-javascript/node-dryice.git repository. Once it done/uploaded to unstable, we will be able to build source-map. I can help about that, Great! but could you find out about the dependency loop: dryice depends on uglify-js I suspect that such dependency would be only needed only for browser use, not for use in a Nodejs environment (which includes build environment for UglifyJS2). If that's true, I suggest to simply add hinting as documented here: https://wiki.debian.org/BuildProfileSpec I don't understand how that helps. In fact we have a simple uglify - sourcemap+dryice - uglify dependency loop. Sorry - I was thinking *build*-dependency loop. You are right, such hinting is of no help here. We could patch a little dryice so that it doesn't Depends uglify-js but only Recommends or Suggests it. Do i remember well ? would that be enough ? Sounds good. My mistake, dryice is tied to uglify too much - it uses uglify's Abstract Syntax Tree to walk the code and find 'require(module)'. I cannot make that optional without cutting dryice legs. On the other hand, uglifyjs2 only needs source-map for the cases where one uses --source-map, something that is not used by source-map (pardon the tautology). I'll push this evening a patch on the master-experimental branch of uglifyjs, just tell me if that's not right. Jérémy. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745687: [Pkg-javascript-devel] Bug#745687: Bug#745687: new upstream version (2.x series)
Hi Jonas, On 30 April 2014 02:10, Jonas Smedegaard d...@jones.dk wrote: Status of packaging is that these libraries needs packaging first: node-source-map node-uglify-to-browserify About node-uglify-to-browserify: You do not really need to package it, since it's only related to uglify2.x (it has no reverse-dependency) I think you can bundle it as a patch along with uglify v2.x. About node-source-map: It build-depends on dryice (=0.4.8). You can find a pre-release package in pkg-javascript/node-dryice.git repository. Once it done/uploaded to unstable, we will be able to build source-map. Regards, Leo. -- Ubuntu Member - http://launchpad.net/~l3on Home Page - http://leoiannacone.com GPG Key Id - 0xD282FC25 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
