Hi
however unlike an iphone Bioconductor is only (as far as I know)
supported for the current release. We all do our best to help users
when they find problems and in most cases when I have suggested they
upgrade they have done so- solving their problems. If they were more
aware of being using an
Hi,
there is benefit in having newest versions, but I think we shouldn't get
carried away, and find Martin's suggestion reasonable. I don't want to be told
to go get an iPhone 5 every time I update an app on my iPhone 4 - even if that
same app would work much better there. People may have legiti
Martin, Herve, Simon, et al,
i see a straightforward approach without the need to change biocLite()
or BiocInstaller behavior. what about every package deciding in loading
time to tell or not the user whether he/she should be using the latest
version of the package, if he/she is not using it?
Hi
I second improving the awareness of users about new Bioc releases and
also personally do not mind loud messages while I am
installing/upgrading packages, even if it is each time I source/run
biocLite(). Indeed for old releases that I maintain for old projects
very rarely have to install a new p
Hi Martin
good to see that Herve agrees with me, and I reiterate my point, because
I consider this issue very important.
The average user does _not_ expect that a function like 'biocLite',
which has the express purpose of downloading and installing packages,
does not pull the newest package.
On 06/19/2013 11:17 PM, Hervé Pagès wrote:
Martin,
Just to make sure we are on the same page, we are talking about
the message we get when we source http://bioconductor.org/biocLite.R
(as Simon suggested), not the message we get when loading the
BiocInstaller package and/or everytime we use bioc
Martin,
Just to make sure we are on the same page, we are talking about
the message we get when we source http://bioconductor.org/biocLite.R
(as Simon suggested), not the message we get when loading the
BiocInstaller package and/or everytime we use biocLite().
So it's a one time thing. IMO it ca
On 06/19/2013 09:15 PM, Hervé Pagès wrote:
Hi Martin,
On 06/19/2013 05:21 PM, Martin Morgan wrote:
On 06/19/2013 03:01 PM, Simon Anders wrote:
Hi
On 19/06/13 23:44, Martin Morgan wrote:
As a message (not warning or error), how about
New features are available in Bioconductor version 2.12
Hi Martin,
On 06/19/2013 05:21 PM, Martin Morgan wrote:
On 06/19/2013 03:01 PM, Simon Anders wrote:
Hi
On 19/06/13 23:44, Martin Morgan wrote:
As a message (not warning or error), how about
New features are available in Bioconductor version 2.12, R version
3.0.1.
See http://bioconducto
On 06/19/2013 03:01 PM, Simon Anders wrote:
Hi
On 19/06/13 23:44, Martin Morgan wrote:
As a message (not warning or error), how about
New features are available in Bioconductor version 2.12, R version
3.0.1.
See http://bioconductor.org/install
and if the instructions / dire consequences
Hi,
I support this too.
On 06/19/2013 02:44 PM, Martin Morgan wrote:
On 06/19/2013 02:24 PM, Laurent Gautier wrote:
I support this.
A notice that there is a newer version available is something a number
of users
would almost expect (since a number of the applications they use probably
already
Hi
On 19/06/13 23:44, Martin Morgan wrote:
As a message (not warning or error), how about
New features are available in Bioconductor version 2.12, R version
3.0.1.
See http://bioconductor.org/install
and if the instructions / dire consequences at
http://bioconductor.org/install are not s
On 06/19/2013 02:24 PM, Laurent Gautier wrote:
I support this.
A notice that there is a newer version available is something a number of users
would almost expect (since a number of the applications they use probably
already do so), and would be in aligned with the bioconductor effort to reach
t
I support this.
A notice that there is a newer version available is something a number
of users would almost expect (since a number of the applications they
use probably already do so), and would be in aligned with the
bioconductor effort to reach the widest possible audience.
However, users
Hi
I would like to suggest the floowing change to the biocLite.R script: As
soon as it is sourced, it should check whether the R interpreter it is
running in has at least the current major version number, and if not,
display a conspicious warning such as
"WARNING: You are not using a current
15 matches
Mail list logo
