On 4 April 2014 at 09:52, Julian Gilbey wrote: | Some examples of other packages which use this system (some calling it | -abi and others -api): | | apache2-bin, banshee, geany, libhdb9-heimdal, python-numpy, | python-sip, erlang-base
Appreciate the list. That is helpful. | It would also mean that the critical r-base transition to testing can | only happen when all of the depending add-on packages have been | upgraded or removed from testing, making the transition far, far | smoother. Yes, it may only happen once every five years, but the pain | was significant last time, and this is a very simple way to avoid that | next time round. This is where we differ. I did not see the last (or previous) transition as painful. At all. [1] I would submit that we could ask on r-sig-debian to see if someone reports about pain. Quite frankly, I have seen more issues (outside of Debian, mostly) with the imposed build change in my Rcpp package (where again within Debian I simply released the four reverse depends the next time). Dirk [1] I have one persistent pain point, but that is unrelated to the transition and your proposal. Well maybe it is related: there are group-maintained r-cran-* packages that are simply poorly maintained. Look at the Debian QA pages, some slip behind a few upstream releases. In that context I do not want a poorly maintained package to block the transitiont of R itself. -- Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
