On Tue, May 28, 2013 at 04:20:28PM +0200, Vincent Danjean wrote: > Of course, all of this will really works once all packages > in testing/unstable depending on "r-base-core (>=3.xxx)" will > have disappear (ie once all of them will have been rebuilt > with the new dependency).
There's no particular need to remove the r-base-core (>= 3.xxx) dependency; it could be generated *in addition to* the r-api-3.0 dependency. However, I would encourage any R policy that may be written to say that the Build-Depends dependency should be r-base-dev (>= XXXX), where XXXX is the minimum version required by the package itself. So if the package only requires R version 2.12, then this should be r-base-dev (>= 2.12). Then if it is built on a wheezy system, it will have a run-time Depends: r-base-core (>= 2.15.1-4), if on jessie (at the time of writing), it will Depends: r-base-core (>= 3.0.0-2) and if on sid, it would be Depends: r-base-core (>= 3.0.1-3), r-api-3.0. Then again, if the r-base-core dependency is dropped and this alternative proposal is used instead of (rather than in addition to the versioned dependency), the sid dependency would just be Depends: r-api-3.0; a specific r-base-core versioned dependency would only be necessary if new features of R 3.1.0, say, were being used. > Note: is you really do not want to rename you r-base-core package, > you can keep it but you then will need to add a versionned Breaks: > dependency for all previous (before R 3.x) Debian R-packages. > As I know that there exists lots of Debian R packages outside > of the main archive, it seems to me that this is a worst solution > as a rename of r-base-core. That is probably not necessary. Someone using testing has to be aware of the possibility of breakages. By the time jessie is released, in two or three years' time, this issue will have been resolved and everyone building external packages should have figured out the new system. Also, the breakages are very obvious: R tells you explicitly that the package needs recompiling with R 3.0.0. Having to rename r-base-core every time there is an API upgrade seems like a kludge, and there would need to be a meta-package which depends on the correct API version, and then people would depend on that meta-package rather than the correct API package.... Julian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
