Re: [Pkg-javascript-devel] please push all node-postgres gbp branches
On 6 September 2014 14:30, Jonas Smedegaard d...@jones.dk wrote: Quoting Jérémy Lal (2014-09-06 14:16:21) Le samedi 06 septembre 2014 à 12:59 +0200, Jonas Smedegaard a écrit : Quoting Jérémy Lal (2014-09-06 08:07:46) i just noticed that there was something missing to the gbp repo. Right - thanks for spotting that. I've pushed in now, and will finalize that (old!) release now. Besides that, will you have time to update it ? It's at 3.4.2 now. Newest node-postgres seems to need these modules missing in Debian: buffer-writer: 1.0.0, pgpass: 0.0.3, packet-reader: 0.2.0, pg-connection-string: 0.1.1, pg-types: 1.4.0 Help is much appreciated getting those packaged! I'm pretty sure i could team up with Leo (if he's available) to get the packages done in the day... but there's an ongoing discussion about bundling modules, so i wonder if it is a good occasion to start one. What do you think ? I am no fan of bundling! I appreciate the concern for keeping resources tight, but have seen no actual measurements as to the damage caused by tracking upstream projects individually - and I see a real damage to bundling in that it weakens tracking our upstreams (are bundled jQuery plugins up-to-date? How to check that - as a developer and as a user?). Perl team has recently gone _away_ from bundling modules. ...but I still remember when I adviced you to not taking serious the complaints about the node name - we lost ~3 years on that account :-( So I guess my advice is to _not_ listen directly to what I think, but only take it as inspiration - try distinguish between noise and substantial parts from those frowning upon tiny packages. I agree that a package containing essentially a single line of code is insane. What do anyone in the team think? Are we messing up with those small modules? It's not so clear, so far, what to do with this kind of utils. Can we discuss all the pro and cons ? I have never managed bundled-multi-sources packages... And... should we have a max-lines-of-code number under of that the module should go in a multi-module package ? L. ___ 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] please push all node-postgres gbp branches
Quoting Leo Iannacone (2014-09-07 10:21:24) On 6 September 2014 14:30, Jonas Smedegaard d...@jones.dk wrote: Quoting Jérémy Lal (2014-09-06 14:16:21) Le samedi 06 septembre 2014 à 12:59 +0200, Jonas Smedegaard a écrit : Newest node-postgres seems to need these modules missing in Debian: buffer-writer: 1.0.0, pgpass: 0.0.3, packet-reader: 0.2.0, pg-connection-string: 0.1.1, pg-types: 1.4.0 Help is much appreciated getting those packaged! I'm pretty sure i could team up with Leo (if he's available) to get the packages done in the day... but there's an ongoing discussion about bundling modules, so i wonder if it is a good occasion to start one. What do you think ? I am no fan of bundling! I appreciate the concern for keeping resources tight, but have seen no actual measurements as to the damage caused by tracking upstream projects individually - and I see a real damage to bundling in that it weakens tracking our upstreams (are bundled jQuery plugins up-to-date? How to check that - as a developer and as a user?). Perl team has recently gone _away_ from bundling modules. ...but I still remember when I adviced you to not taking serious the complaints about the node name - we lost ~3 years on that account :-( So I guess my advice is to _not_ listen directly to what I think, but only take it as inspiration - try distinguish between noise and substantial parts from those frowning upon tiny packages. I agree that a package containing essentially a single line of code is insane. What do anyone in the team think? Are we messing up with those small modules? If it works, then it works! If you can manage to track upstream changes and keep the bundle-packages sensibly up-to-date and their contents is reasonably easy to locate for our users, then I guess it is a success. And... should we have a max-lines-of-code number under of that the module should go in a multi-module package ? I am sceptical to such quantitative measure. But then again, I am sceptical to the whole approach so should probably step back and let those exploring the approach discuss here :-) My point was not that recent activities on bundling tiny Node packages has failed, but that a) I most likely won't participate in that and b) I recommend to beware if really needed (do the critical voices in Debian indicate real trouble e.g. with Policy or just a loud minority opinion). - 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: 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] please push all node-postgres gbp branches
Le dimanche 07 septembre 2014 à 10:44 +0200, Jonas Smedegaard a écrit : Quoting Leo Iannacone (2014-09-07 10:21:24) On 6 September 2014 14:30, Jonas Smedegaard d...@jones.dk wrote: ../.. And... should we have a max-lines-of-code number under of that the module should go in a multi-module package ? I am sceptical to such quantitative measure. But then again, I am sceptical to the whole approach so should probably step back and let those exploring the approach discuss here :-) My point was not that recent activities on bundling tiny Node packages has failed, but that a) I most likely won't participate in that and b) I recommend to beware if really needed (do the critical voices in Debian indicate real trouble e.g. with Policy or just a loud minority opinion). While i think a package manager is supposed to manage packages, not force upon us arbitrary constraints, i must admit i'm not so happy with many small modules doing the same thing, like the multiplication of async helpers, or ansi tools, or stream tools (which is caused by the absence of a standard library for Node.js). Eventually, in a given category, many modules are going to be removed in favor of one (most popular / technically sound). Instead of waiting for the natural selection to happen, there are several things we could do to fasten the process: * bundle similar modules in the same category * propose a good representant, popular module of that category and progressively patch away all others in the same category * add some compatibility helpers to a representant module to ease replacement of other modules In the end, i'm not sure any of this work will be really useful, since the time spent doing that is time not spent on the quality of existing packages, and i don't think it would be a vast improvement to do that. 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
Re: [Pkg-javascript-devel] please push all node-postgres gbp branches
Hi Jérémy, [I dare reply via our public list - hope you don't mind] Quoting Jérémy Lal (2014-09-06 08:07:46) i just noticed that there was something missing to the gbp repo. Right - thanks for spotting that. I've pushed in now, and will finalize that (old!) release now. Besides that, will you have time to update it ? It's at 3.4.2 now. Newest node-postgres seems to need these modules missing in Debian: buffer-writer: 1.0.0, pgpass: 0.0.3, packet-reader: 0.2.0, pg-connection-string: 0.1.1, pg-types: 1.4.0 Help is much appreciated getting those packaged! - 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: 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] please push all node-postgres gbp branches
Le samedi 06 septembre 2014 à 12:59 +0200, Jonas Smedegaard a écrit : Hi Jérémy, [I dare reply via our public list - hope you don't mind] Quoting Jérémy Lal (2014-09-06 08:07:46) i just noticed that there was something missing to the gbp repo. Right - thanks for spotting that. I've pushed in now, and will finalize that (old!) release now. Besides that, will you have time to update it ? It's at 3.4.2 now. Newest node-postgres seems to need these modules missing in Debian: buffer-writer: 1.0.0, pgpass: 0.0.3, packet-reader: 0.2.0, pg-connection-string: 0.1.1, pg-types: 1.4.0 Help is much appreciated getting those packaged! I'm pretty sure i could team up with Leo (if he's available) to get the packages done in the day... but there's an ongoing discussion about bundling modules, so i wonder if it is a good occasion to start one. What do you think ? 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
