On 11-06-14 7:21 PM, Kornelius Rohmeyer wrote:
2011/6/11 Duncan Murdoch:
[...]
I don't understand. It sounds as though you're saying these two
contradictory things:
- your package works with any version of graph
- CRAN builds a version of graph that is incompatible with your package.
No,
Am 15. Juni 2011 09:19 schrieb Uwe Ligges :
>
>
> On 15.06.2011 01:21, Kornelius Rohmeyer wrote:
>>
>> 2011/6/11 Duncan Murdoch:
>> [...]
>>>
>>> I don't understand. It sounds as though you're saying these two
>>> contradictory things:
>>>
>>> - your package works with any version of graph
>>> -
On 15.06.2011 01:21, Kornelius Rohmeyer wrote:
2011/6/11 Duncan Murdoch:
[...]
I don't understand. It sounds as though you're saying these two
contradictory things:
- your package works with any version of graph
- CRAN builds a version of graph that is incompatible with your package.
N
2011/6/11 Duncan Murdoch :
[...]
> I don't understand. It sounds as though you're saying these two
> contradictory things:
>
> - your package works with any version of graph
> - CRAN builds a version of graph that is incompatible with your package.
No, the first statement is correct but not the
On 11-06-11 1:09 AM, Kornelius Rohmeyer wrote:
2011/6/11 Duncan Murdoch:
On 11-06-10 7:04 PM, Kornelius Rohmeyer wrote:
Dear all,
for a CRAN-package that depends on another Bioconductor-package I find
two things annoying and would like to know whether there are some
workarounds:
1) Is there s
Actually I do not understand what is so hard to understand with CRAN policy.
This is:
Any source package on CRAN is build in binary form with
R-release/patched and R-oldrelease. This does not happen if you tell
your package it requires a particular R version - such as the
declaration R (>= 2.1
2011/6/11 Prof Brian Ripley :
> On Sat, 11 Jun 2011, Kornelius Rohmeyer wrote:
>> 2011/6/11 Prof Brian Ripley :
>>> Note that until May 8 graph was a CRAN packge and the current version was
>>> 1.30.0. So of course CRAN binary packages built between April 26 and May
>>> 8
>>> were built against th
On Sat, 11 Jun 2011, Kornelius Rohmeyer wrote:
2011/6/11 Prof Brian Ripley :
Note that until May 8 graph was a CRAN packge and the current version was
1.30.0. So of course CRAN binary packages built between April 26 and May 8
were built against the current CRAN version of graph, for any versio
2011/6/11 Prof Brian Ripley :
> Note that until May 8 graph was a CRAN packge and the current version was
> 1.30.0. So of course CRAN binary packages built between April 26 and May 8
> were built against the current CRAN version of graph, for any version of R.
Thanks for the notice! But if I am n
Note that until May 8 graph was a CRAN packge and the current version
was 1.30.0. So of course CRAN binary packages built between April 26
and May 8 were built against the current CRAN version of graph, for
any version of R.
On Fri, 10 Jun 2011, Martin Morgan wrote:
On 06/10/2011 05:46 PM,
2011/6/11 Duncan Murdoch :
> On 11-06-10 7:04 PM, Kornelius Rohmeyer wrote:
>> Dear all,
>>
>> for a CRAN-package that depends on another Bioconductor-package I find
>> two things annoying and would like to know whether there are some
>> workarounds:
>>
>> 1) Is there some inevitable problem that i
2011/6/11 Martin Morgan :
> On 06/10/2011 05:46 PM, Kornelius Rohmeyer wrote:
>>
>> Dear Martin,
>>
>> thanks for your response.
>>
The superclass graphBase is introduced in graph 1.30. In my
understanding the problem is that our package gMCP is build on CRAN
for R 2.12 with the pack
On 06/10/2011 05:46 PM, Kornelius Rohmeyer wrote:
Dear Martin,
thanks for your response.
The superclass graphBase is introduced in graph 1.30. In my
understanding the problem is that our package gMCP is build on CRAN
for R 2.12 with the package graph in version 1.30. Unfortunately
biocLite ins
Dear Martin,
thanks for your response.
>> The superclass graphBase is introduced in graph 1.30. In my
>> understanding the problem is that our package gMCP is build on CRAN
>> for R 2.12 with the package graph in version 1.30. Unfortunately
>> biocLite installs graph_1.28.0.zip for R 2.12.
>
> bi
On 11-06-10 7:04 PM, Kornelius Rohmeyer wrote:
I'm sorry for sending a wrongly formated mail before. This is the missing text:
Dear all,
for a CRAN-package that depends on another Bioconductor-package I find
two things annoying and would like to know whether there are some
workarounds:
1) Is t
On 06/10/2011 04:04 PM, Kornelius Rohmeyer wrote:
I'm sorry for sending a wrongly formated mail before. This is the missing text:
Dear all,
for a CRAN-package that depends on another Bioconductor-package I find
two things annoying and would like to know whether there are some
workarounds:
1) I
I'm sorry for sending a wrongly formated mail before. This is the missing text:
Dear all,
for a CRAN-package that depends on another Bioconductor-package I find
two things annoying and would like to know whether there are some
workarounds:
1) Is there some inevitable problem that install.package
Dear all,
for a CRAN-package that depends on another Bioconductor-package I find two
things annoying and would like to know whether there are some workarounds:
1) Is there some inevitable problem that install.packages does not install
uninstalled packages (on which the specified package depends)
18 matches
Mail list logo
