Hi, Hervé,
Hi, Bioc-devel folks,
Is there an accepted way to migrate a package from CRAN to BioC?
CRAN's policy says, "The package�s license must give the right for
CRAN to distribute the package in perpetuity."...
Is it enough to request that CRAN archive the package, then submit it
as a n
Hi Gordon,
On 03/04/2015 02:12 PM, Gordon Brown wrote:
Hi,
Hi, Bioc-devel folks,
Is there an accepted way to migrate a package from CRAN to BioC?
CRAN's policy says, "The package�s license must give the right for
CRAN to distribute the package in perpetuity."...
Is it enough to request tha
On Wed, Mar 4, 2015 at 1:27 PM, Laurent Gatto wrote:
>
> On 3 March 2015 06:07, Henrik Bengtsson wrote:
>
>> Not that long ago DESCRIPTION field 'Additional_repositories' was
>> introduced which the purpose of providing references to non-mainstream
>> package repositories, e.g. R-Forge. Interest
Hi,
> > Hi, Bioc-devel folks,
> >
> > Is there an accepted way to migrate a package from CRAN to BioC?
> > CRAN's policy says, "The package�s license must give the right for
> > CRAN to distribute the package in perpetuity."...
> >
> > Is it enough to request that CRAN archive the package, then s
On 3 March 2015 06:07, Henrik Bengtsson wrote:
> Not that long ago DESCRIPTION field 'Additional_repositories' was
> introduced which the purpose of providing references to non-mainstream
> package repositories, e.g. R-Forge. Interestingly, by "mainstream"
> they mean CRAN and Bioconductor. Th
- Original Message -
> From: "Gordon Brown"
> To: bioc-devel@r-project.org
> Sent: Wednesday, March 4, 2015 3:30:35 AM
> Subject: Re: [Bioc-devel] CRAN package with Bioconductor dependencies
>
> Hi, Bioc-devel folks,
>
> Is there an accepted way to m
Hi, Bioc-devel folks,
Is there an accepted way to migrate a package from CRAN to BioC? CRAN's policy
says, "The package�s license must give the right for CRAN to distribute the
package in perpetuity."...
Is it enough to request that CRAN archive the package, then submit it as a new
package to
Not that long ago DESCRIPTION field 'Additional_repositories' was
introduced which the purpose of providing references to non-mainstream
package repositories, e.g. R-Forge. Interestingly, by "mainstream"
they mean CRAN and Bioconductor. The 'Additional_repositories' field
is also enforced for CRA
Thank you all for your answers.
Laurent
On 2 March 2015 23:27, Martin Morgan wrote:
> On 03/02/2015 03:18 PM, Laurent Gatto wrote:
>>
>> Dear all,
>>
>>
>> I had never realised that CRAN packages that depended on Bioc packages
>> could actually not be installed with install.packages without se
Hi Laurent,
On 03/02/2015 03:18 PM, Laurent Gatto wrote:
Dear all,
I had never realised that CRAN packages that depended on Bioc packages
could actually not be installed with install.packages without setting a
repo or using BiocInstaller::bioLite. Here is an example using a fresh R
installati
On 03/02/2015 03:22 PM, Ryan C. Thompson wrote:
I thought CRAN packages weren't allowed to depend on Bioconductor packages for
exactly this reason.
CRAN packages can and do depend on Bioconductor packages.
The different versioning schemes use by CRAN and by Bioconductor can lead to
confusion,
Even if it is allowed, what is the reasoning behind not simply putting the
package in Bioconductor? It seems like a fair bit of pain for very little
benefit.
~G
On Mon, Mar 2, 2015 at 3:22 PM, Ryan C. Thompson
wrote:
> I thought CRAN packages weren't allowed to depend on Bioconductor packages
>
On 03/02/2015 03:18 PM, Laurent Gatto wrote:
Dear all,
I had never realised that CRAN packages that depended on Bioc packages
could actually not be installed with install.packages without setting a
repo or using BiocInstaller::bioLite. Here is an example using a fresh R
installation
http:/
I thought CRAN packages weren't allowed to depend on Bioconductor
packages for exactly this reason.
On 03/02/2015 03:18 PM, Laurent Gatto wrote:
Dear all,
I had never realised that CRAN packages that depended on Bioc packages
could actually not be installed with install.packages without setti
Dear all,
I had never realised that CRAN packages that depended on Bioc packages
could actually not be installed with install.packages without setting a
repo or using BiocInstaller::bioLite. Here is an example using a fresh R
installation
http://cran.r-project.org/web/packages/MSeasy/index.ht
15 matches
Mail list logo
