Hi,
On Fri, 14 Mar 2025 at 15:53, Marcel Ramos
wrote:
>
> Hi,
>
> On 3/14/25 5:42 AM, Lluís Revilla wrote:
>
> Hi!
>
> Before moving to git (and shortly after), Bioconductor used to support
> these kind of files.
>
> Can you point to where in the documentation these files were supported?
I don't
Hi,
On 3/14/25 5:42 AM, Lluís Revilla wrote:
> Hi!
>
> Before moving to git (and shortly after), Bioconductor used to support
> these kind of files.
Can you point to where in the documentation these files were supported?
> One can still find repositories with these files on code.bioconductor.org
Hi!
Before moving to git (and shortly after), Bioconductor used to support
these kind of files.
One can still find repositories with these files on code.bioconductor.org.
As these files are optional and might not even be described by
guidelines they do not bother new developers (or Bioconductor c
Hi Leonardo,
BioC doesn't oppose an Rmd -- you just need to include the eval=F in the
package installation code chunk. If helpful, please have a look at our
package GitHub:
https://bioconductor.org/packages/release/bioc/html/rhinotypeR.html
Best,
Martha
On Tue, 11 Mar 2025 at 14:05, Leonardo Co
Hi Leo!
As Martha responded, there is no issue with having a README.Rmd in the
package folder.
(The section is not so clear and could use some revision)
Note that some authors maintain a README.md file without an Rmd.
For some of my packages, I re-use the vignette to generate the README.md
file.
