On 22 November 2012 at 22:41, Steffen Neumann wrote:
| Hi,
|
| On Thu, 2012-11-22 at 15:22 -0600, Dirk Eddelbuettel wrote:
| ...
| > But as soon as we change a structure or header somewhere, things potentiall
| > go boom. We try to be careful, but we are also eager to get new "stuff"
out.
|
|
Hi,
On Thu, 2012-11-22 at 15:22 -0600, Dirk Eddelbuettel wrote:
...
> But as soon as we change a structure or header somewhere, things potentiall
> go boom. We try to be careful, but we are also eager to get new "stuff" out.
New stuff is great! The problem is if the ABI changes,
and normal share
On 22 November 2012 at 21:05, Laurent Gatto wrote:
| On 22 November 2012 20:37, Steffen Neumann wrote:
| > Hi,
| >
| > thanks Dan for fixing this. I can vaguely remember
| > we've had such a problem before.
|
| We had this issue 6 months ago, when Rcpp 0.9.12 was released (see [1]
| and commit r
On 22 November 2012 20:37, Steffen Neumann wrote:
> Hi,
>
> thanks Dan for fixing this. I can vaguely remember
> we've had such a problem before.
We had this issue 6 months ago, when Rcpp 0.9.12 was released (see [1]
and commit r67124).
> Is there any way to avoid that problem in the future ?
>
Hi,
thanks Dan for fixing this. I can vaguely remember
we've had such a problem before.
Is there any way to avoid that problem in the future ?
Is it that BioC needs to recompile packages when
their dependencies change ?
Or should we have some *maximum* Rcpp version number
in the mzR dependen
