Re: R 3.0.0 and required rebuilds of all reverse Depends: of R
- To: firstname.lastname@example.org
- Subject: Re: R 3.0.0 and required rebuilds of all reverse Depends: of R
- From: Don Armstrong <email@example.com>
- Date: Mon, 1 Apr 2013 09:54:51 -0700
- Message-id: <[🔎] 20130401165451.GY4247@rzlab.ucr.edu>
- Mail-followup-to: firstname.lastname@example.org
- In-reply-to: <email@example.com>
- References: <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org>
On Sun, 31 Mar 2013, Dirk Eddelbuettel wrote:
> It really does not add much as well already have a, say, Dependds:
> r-base-core (>= 3.0.0~20130327) so we are really just trading one
> for the other as far as I can tell.
The difference is that you can do the following:
r-base-core Provides: r-base-api-3
and all cran depends on r-base-api-3.
When the API changes incompatibly, and an entire rebuild is required,
you change the api, so that r-base-core now Provides r-base-api-4.
Now, all cran packages have to be upgraded in lockstep with R, and you
cannot have R packages installed which are incompatible with the R
The version number attached to the API only increments when the API
changes incompatibly. If the API changes in a complex way, you could
also conceivably provide multiple versions of the API in the base
Tell me something interesting about yourself.
Lie if you have to.
-- hugh macleod http://www.gapingvoid.com/archives/batch20.php