Re: bioinformatics.scm vs bioconductor.scm ?

2018-12-20 Thread Ricardo Wurmus
Ricardo Wurmus writes: >> Is the bioconductor importer usable from `guix import` ? > > yes. You may encounter minor problems when using the recursive > bioconductor importer, as it may try to look up CRAN packages on > Bioconductor. This is now fixed in commit 10a1cacb1. The importer will

Re: bioinformatics.scm vs bioconductor.scm ?

2018-12-18 Thread Ricardo Wurmus
zimoun writes: > Ok, but for example this convention about CRAN is not consistent with > the importer. :-) > guix import cran corpcor -r > fills the license field with (license gpl3+) and not (license license:gpl3+) That’s right. The importer does not know where the generated package

Re: bioinformatics.scm vs bioconductor.scm ?

2018-12-18 Thread Ricardo Wurmus
Hi, > Is the bioconductor importer usable from `guix import` ? yes. You may encounter minor problems when using the recursive bioconductor importer, as it may try to look up CRAN packages on Bioconductor. > This package is on Bioconductor: >

Re: bioinformatics.scm vs bioconductor.scm ?

2018-12-18 Thread zimoun
Dear, Thank you for your explanations. And sorry if I am still slow to understand. > > What is the convention about license ? > > (license name) or (license license:name) > > Just about this point: This is not a "convention", this is part of the > language definition of Guile, the underlying

Re: bioinformatics.scm vs bioconductor.scm ?

2018-12-18 Thread Björn Höfling
On Tue, 18 Dec 2018 06:31:44 -0500 zimoun wrote: > What is the convention about license ? > (license name) or (license license:name) Just about this point: This is not a "convention", this is part of the language definition of Guile, the underlying Scheme implementation: In the module

Re: bioinformatics.scm vs bioconductor.scm ?

2018-12-18 Thread zimoun
Dear Ricardo, Thank you for your explanations. > > And I am asking myself if a massive import from Bioconductor should be > > possible ? > > Certainly! I’ve done this before actually, but I hit two minor > problems: > > 1. the bioconductor recursive importer does not *automatically* switch >

Re: bioinformatics.scm vs bioconductor.scm ?

2018-12-12 Thread Ricardo Wurmus
zimoun writes: > Thank you the explanations. > > >> New Bioconductor packages should go to bioconductor.scm. Eventually we >> may move all remaining R packages from bioinformatics to >> bioconductor.scm. > > I am a bit confused. > The file bioconductor.scm contains (or will contain) all R

Re: bioinformatics.scm vs bioconductor.scm ?

2018-12-12 Thread zimoun
Thank you the explanations. > New Bioconductor packages should go to bioconductor.scm. Eventually we > may move all remaining R packages from bioinformatics to > bioconductor.scm. I am a bit confused. The file bioconductor.scm contains (or will contain) all R packages from Bioconductor, right?

Re: bioinformatics.scm vs bioconductor.scm ?

2018-12-11 Thread Ricardo Wurmus
zimoun writes: > I am not sure to understand what is the rule to attribute a package to > bioinformatics.scm or to bioconductor.scm when it comes from > Bioconductor. bioinformatics.scm was there first. Later I added bioconductor.scm because I didn’t want bioinformatics.scm to eventually be

bioinformatics.scm vs bioconductor.scm ?

2018-12-11 Thread zimoun
Dear, Thank you the nice importers. I am not sure to understand what is the rule to attribute a package to bioinformatics.scm or to bioconductor.scm when it comes from Bioconductor. For example, the package DeSeq2 from Bioconductor is in bioinformatics.scm. To be concrete, $ grep -e