Another concern with kent utils (as opposed to kent lib) is the
non-open-source licensing.
Michael
On Sat, Aug 18, 2018 at 10:11 AM, Tim Triche, Jr. wrote:
> Vince beat me to it. Don’t use Kent utils unless you have to. If you have
> something like a bigBed parser, I could perhaps help clean it
Vince beat me to it. Don’t use Kent utils unless you have to. If you have
something like a bigBed parser, I could perhaps help clean it up. But if you’re
doing anything that could possibly be done in Rsamtools or rtracklayer, I would
join Vince in urging you to use their functions. You will have
On Sat, Aug 18, 2018 at 12:17 PM, Ghiwa Khalil wrote:
> Hello,
>
> We are writing a package with 2 main functions, one of these functions
> requires kent utils to be installed.
>
> Since kent utils is supported by only specific operating systems, is it
> recommended to have it in an R package?
>
Hello,
We are writing a package with 2 main functions, one of these functions
requires kent utils to be installed.
Since kent utils is supported by only specific operating systems, is it
recommended to have it in an R package?
If we remove this function then our package will only be based on one
