Am Mo., 13. Dez. 2021 um 14:24 Uhr schrieb Kern, Lori <
lori.sheph...@roswellpark.org>:
> I don't see any changes on the RELEASE_3_14 branch. Please make sure to
> push to the RELEASE_3_14 branch […]
>
Understood! Done, I cherry-picked all the commits over.
Am Mo., 13. Dez. 2021 um 19:39 Uhr
On 12/12/2021 03:49, Philipp A. wrote:
I think the easiest fix was to just switch to HTML vignettes, then destiny
is no longer dependent on Bioconductor’s LaTeX environment staying stable.
Let’s see in the next build if it worked.
Just in case someone is watching this thread and wondering
Hi Brian,
Note that Rsamtools does not relies on any CLI tools. It contains C/C++
code that is _compiled_ and _linked_ against Rhtslib rather than relying
on the standalone `samtools` and `tabix` commands.
Installing MAGMA at package installation time in the package
installation folder of
Thank you both for the helpful feedback. I’ll follow up with the developers of
MAGMA for clarification on license.
Regarding installation, I agree Kasper, this is not an ideal solution.
Installing MAGMA at the R package installation time would be ideal, but I’ve
been unable to come up with a
Ignoring the license issues (which may be significant), I strongly dislike
this installation strategy. It (IMO) unreasonable that you potentially
write in system locations on package load. You're looking in
/usr/local/bin
R.home/bin <- this makes not sense, this is the R home location, why
I don't see any changes on the RELEASE_3_14 branch. Please make sure to push
to the RELEASE_3_14 branch as described in
http://bioconductor.org/developers/how-to/git/bug-fix-in-release-and-devel/
Pushing to the master branch will not have the changes reflected at:
