On 26/10/2017 12:50 PM, Bruce Hoff wrote:
I respectfully disagree that it's "fragile" to depend on a particular
version of a package. On the contrary I think it's the foundation of
making software stable.
In general that might be true, but for R it's not. If mypackage
requires version 1.7.0
FWIW the patches in 1.6.3 are always a part of 1.7.0 -- its just that 1.7.0
has a lot of other new stuff in it as well and enterprises are sometimes
more likely to upgrade to a patch release rather than the next minor
version.
Overall I think my understanding from this thread is that one should se
I respectfully disagree that it's "fragile" to depend on a particular
version of a package. On the contrary I think it's the foundation of
making software stable. Having said this, reading the rest of your
description of how CRAN works is enlightening and emphasizes an underlying
philosophy about
On 26/10/2017 10:36 AM, Bruce Hoff wrote:
Hi:
I think this would make life harder for CRAN and for other developers,
so it's unlikely to happen.
For example, suppose both yourpackage 1.6.3 and 1.7.0 are active on
CRAN, and mypackage declares that it depends on yourpackage. Then if I
upload an
Hi:
> I think this would make life harder for CRAN and for other developers,
> so it's unlikely to happen.
> For example, suppose both yourpackage 1.6.3 and 1.7.0 are active on
> CRAN, and mypackage declares that it depends on yourpackage. Then if I
> upload an update to mypackage, which version
Hi,
2017-10-26 5:16 GMT+02:00 Peter Dunn :
> Hi all
>
> I am trying to compile (on my Mac) an R package (tweedie) which includes
> Fortran 77 code. I’m not much of a programmer, but can still manage to write
> and update F77 code. I’m new to valgrind.
>
> In checking my package (which passes the
