- Original Message -
> From: "Hervé Pagès"
> To: "Laurent Gatto" , bioc-devel@r-project.org
> Sent: Thursday, October 30, 2014 10:52:14 AM
> Subject: Re: [Bioc-devel] experiment data package versioning
>
> Hi Laurent,
>
> On 10/30/2014 10:31 AM, Laurent Gatto wrote:
> > Dear all,
> >
>
Hi Laurent,
On 10/30/2014 10:31 AM, Laurent Gatto wrote:
Dear all,
I was under the (wrong) impression that experiment data packages would
be following the same versioning convention as software with even/odd
for release/devel branches.
You're right! This is what we should have done:
https:
On 30 October 2014 17:43, Henrik Bengtsson wrote:
> On Thu, Oct 30, 2014 at 10:31 AM, Laurent Gatto wrote:
>> Dear all,
>>
>> I was under the (wrong) impression that experiment data packages would
>> be following the same versioning convention as software with even/odd
>> for release/devel branc
- Original Message -
> From: "Henrik Bengtsson"
> To: "Laurent Gatto"
> Cc: bioc-devel@r-project.org
> Sent: Thursday, October 30, 2014 10:43:11 AM
> Subject: Re: [Bioc-devel] experiment data package versioning
>
> On Thu, Oct 30, 2014 at 10:31 AM, Laurent Gatto
> wrote:
> > Dear all,
On Thu, Oct 30, 2014 at 10:31 AM, Laurent Gatto wrote:
> Dear all,
>
> I was under the (wrong) impression that experiment data packages would
> be following the same versioning convention as software with even/odd
> for release/devel branches.
>
> Would this be something that others would find use
Dear all,
I was under the (wrong) impression that experiment data packages would
be following the same versioning convention as software with even/odd
for release/devel branches.
Would this be something that others would find useful?
Best wishes,
Laurent
___
- Original Message -
> From: "Gabe Becker"
> To: bioc-devel@r-project.org, "Jim Fitzgerald"
> Sent: Thursday, October 30, 2014 10:21:17 AM
> Subject: [Bioc-devel] R-devel update schedule/strategy for Bioc devel build
> machines
>
> Bioc admins,
>
> We have an automatic build/test m
Bioc admins,
We have an automatic build/test mechanism for our internal packages which
we'd like to match the Bioc build machines as closely as possible. AFAIU,
the exact commit-specific version of R-devel used on your devel build
server changes occasionally within Bioc releases, and we'd like to
Hi Darin,
We're grateful that you're willing to do this!
Please be aware that a particular version of BioC is aimed
to be used with a particular version of R only. E.g. the current
release (BioC 3.0) is aimed to be used with R-3.1.1. Also some
BioC packages depend on particular versions of CRAN
Hi, Darin.
You might find these instructions useful:
http://www.bioconductor.org/about/mirrors/mirror-how-to/
Basically, you can use rsync to get the repository and keep it up-to-date.
Sean
On Thu, Oct 30, 2014 at 9:17 AM, Darin Perusich wrote:
> Hello All,
>
> Would it be possible to get a
Hello All,
Would it be possible to get a listing of all package sources from
/packages/release/bioc/src/contrib or make the location browseable?
I'm trying to download all the bioconductor tarball's so I can create
rpm packages of them for inclusion in the openSUSE Build Service. I've
already done
11 matches
Mail list logo
