On 28 May 2013 at 14:57, Julian Gilbey wrote:
| On Tue, May 28, 2013 at 08:33:14AM -0500, Dirk Eddelbuettel wrote:
| > | So because of the new version in sid, which didn't wait for the R
| > | 3.0.0 migration to testing, the jessie version is still an R 2.7
| > | version :-(  Had there been a "Provides: r-api-3.0" in r-base-core and
| > | "Depends: r-api-2.7" in r-cran-mgcv, the transition would either have
| > | been delayed or knowingly pushed though in spite of this, but the
| > | breakage would have been caught at the time.  (Then again, this might
| > | have been the case anyway.)
| > 
| > There is no such thing as an "R 2.7" API, and as long as upstream does not
| > define one I do not plan to jump into the frey and meddle with it.
| 
| Oh gosh, my bad (as I said in a follow-on email which crossed in the
| post with yours ;-) - replace that with "R 2.14" or "R 2.10" or
| whenever the last API change happened.
| 
| And I'm certainly not advocating going back and modifying old packages
| retrospectively - I'm only looking to the future.

I am with you on that. Looking back, we good a one-year heads-up for R 3.0.0
breaking.  At that one point I could (and probably should) have added such a
provides.  

We'll do it next time for a known "big breakage".  We should however not go
overboard and add it for R 3.1.0 just because.
 
| > The status quo works well enough, but I will acknowledge the breakage you 
got
| > with that r-cran-mgcv package.  But I think we have bigger fish to fry.
| 
| We do have bigger fish to fry, indeed, but if the next API change
| happens shortly before the next Debian (stable) release, it will be a
| real headache at that point!  It seems so straightforward to pre-empt
| that possibility with very little effort (add a "Provides: r-api-3.0"
| to the r-base-core package and the code appearing earlier in this bug
| report to the r-base-dev package); then an "${R:Depends}" in people's
| source packages will make everything work perfectly in the future.

Agreed in principle.

Ping me off-list for help with r-cran-mgcv rebuilds.  I tend to just stick
things I need into /usr/local/lib/R/ as it is so easy and not all I need
exists as r-cran-* ...

Dirk


-- 
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

Reply via email to