On 29/11/2011 00:16, Jonathan Nieder wrote: > Ian Jackson wrote: > >> I think the best way to fix this is to prepare both renaming uploads >> in advance, and allow either of the two contending maintainers to >> upload both packages simultaneously. > > Thanks, that sounds sensible to me. > > Since this still seems to be stalled, I would like to hear from the > nodejs maintainers whether this approach would be okay with them and > whether there is anything others involved with Debian can do to help > with the migration.
I can prepare a patch for nodejs package. Those matters need help : - All packages shipping files with a node shebang must also be patched. Is there a simple way to search all packages having a node shebang ? - I can't help but talk about "npm", an essential development tool distributed in latest nodejs (can be compared to ruby's gem). It allows one to install and publish npm packages to a common registry. It will need a patch to rename shebangs on-the-fly, and maybe rename them back when publishing. Npm author is working closely with nodejs authors. > (Yes, that includes helping talk with upstream to get nodejs accepted > as a synonym so scripts with "#!/usr/bin/env nodejs" can work > everywhere. Convincing upstream will obviously need treasures of diplomacy, as it's easier for them to point their users to alternative debian packages. > Yes, that includes changing policy, if you happen to have > a coherent proposal in mind.) I don't understand, could you explain why / which policy ? Jérémy. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ed425ff.6010...@edagames.com
