gt; development
> that arise from Bioconductor's package guidelines.
>
> I don't think we want to change the limits on package payload
> size without
> understanding the consequences for users and our build
> system. The split
> ap
gt; development
> that arise from Bioconductor's package guidelines.
>
> I don't think we want to change the limits on package payload
> size without
> understanding the consequences for users and our build
> system. The split
> ap
Hi Adam,
I also got this problem, and I would like some input from Bioc Core
Team. I worked around it by writing a minimal vignette in the main
branch. Then I made a documentation branch, where I have the same code
as in main branch, but with more elaborate vignettes used to build a
pkgdown
Hi Adam,
I also got this problem, and I would like some input from Bioc Core
Team. I worked around it by writing a minimal vignette in the main
branch. Then I made a documentation branch, where I have the same code
as in main branch, but with more elaborate vignettes used to build a
pkgdown
Hi,
I would like to add a new author to the packages Voyager and SFEData, of
which I'm an original author, and give her git commit access to the
repos on Bioconductor. Her email is kayla...@caltech.edu
Thanks,
Lambda
___
Bioc-devel@r-project.org
Hi,
I would like to add a new author to the packages Voyager and SFEData, of
which I'm an original author, and give her git commit access to the
repos on Bioconductor. Her email is kayla...@caltech.edu
Thanks,
Lambda
___
Bioc-devel@r-project.org
