On Thu, Apr 17, 2014 at 9:43 PM, Simon Urbanek
<simon.urba...@r-project.org>wrote:
[...]
> The Suggests failure has nothing to do with BioC. Only packages listed in
> Depends/Imports are required for a package to work so there is no guarantee
> for any packages in Suggests to be available - hence the package should not
> break if they are not available - that's the whole point of Suggests. If
> you list it in Depends/Imports then it won't even get to the check if those
> packages are not available - it won't build at all. I didn't look at the
> dependencies in this particular case, but one reason to use Suggests is to
> break dependency loops: if A depends on B and B on A, then there is no way
> to install them, so typically A suggests B and B depends on A so that A can
> be installed and checked first without B and then B checked with A and
> finally A with B.
>
I would naively think that if you install A and B _together_, then they
should be fine. At least this is how dependencies work on various Linux
distributions, AFAIK.
> If A breaks without B then it makes such bootstrapping impossible - we
> found some packages with this issue, that's why mentioned this - I don't
> know if that's the case with igraph or not.
>
> As for BioC, the builds for BioC are independent of CRAN, so CRAN doesn't
> build BioC packages and thus their availability is subject to manual
> intervention - on the OS X build machine there is currently no automated
> way to track BioC packages, but we're working on it.
>
So this effectively means that if I Import/Depend/Suggest etc. a BioC
package in igraph, then igraph will likely not be available for OSX. Right?
Gabor
>
> Cheers,
> Simon
>
>
[[alternative HTML version deleted]]
______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
