Hi Julian
what if two Bioc packages require different version of the ‘same’ CRAN package?
AfaIu, the infrastructure is not designed to deal with multiple versions of a
package.
Nor would I as a user expect to have less-than-the-most recent versions of CRAN
packages in my library just because some other package says so…
Just to throw in another, and probably silly suggestion: the Bioconductor
repository could keep ‘snapshots’ of CRAN packages compatible with each
release, but they would have to be name-mangled in some way. The potential for
confusion is enormous.
Best wishes
Wolfgang
Il giorno 22 Apr 2014, alle ore 16:14, Julian Gehring <julian.gehr...@embl.de>
ha scritto:
> Hi,
>
> For a "more general solution" one could think of specifying the version of
> critical packages in the 'description' file and having a 'biocLite' function
> that installs the specific version from CRAN. See e.g. the
> 'devtools::install_version' function for installing older packages from the
> CRAN archive. This may have drawbacks for binary or compiled packages though.
>
> Best wishes
> Julian
>
>
> On 22.04.2014 15:31, Alejandro Reyes wrote:
>>
>> However, I don't know if this could be a "general solution for all
>> users" since when installing a package via
>> biocLite, the latest version of the cran package is installed
>> regardless the R/BiocInstaller version you are using. Users
>> would need to download the versions of the dependencies that they need
>> and install them manually.
>
> _______________________________________________
> Bioc-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/bioc-devel
_______________________________________________
Bioc-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel
