Quoting Jérémy Lal (2013-09-01 17:57:17) > On 01/09/2013 12:46, Jonas Smedegaard wrote: > > Quoting Jérémy Lal (2013-08-31 10:01:11) > >> It is upstream's goal to improve on this, meanwhile it means > >> the next stable release of nodejs will have to Break all c++ > >> modules (at their current versions). > >> Is there a way to ease transition that right now ? > >> Add nodejs << 0.11 in Depends ? > > > > If what breaks is abi but not api, then I believe the best is to > > release with no Breaks, and then request binNMUs for all affected > > reverse dependencies. > > no no it is really API breaking, both forward and backward. When > nodejs is 1.0 these matters are supposed to be solved.
Oh, ok. In that case it seems sensible to me to add Breaks in nodejs package against all reverse dependencies, up to and including the exact current version. E.g. "Breaks: node-pg (<= 0.7.1-1)". That covers current version but not eventual binNMUs. I believe it is wrong to use an explicit version that does not really exist yet - so even if adding a trailing "+" would technically work I believe that is wrong. (as a sidenote, I _do_ find it ok to add training "~" for versioned dependencies, to include eventual backports of same version). - 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
