From krcoombes at mdacc.tmc.edu  Mon Dec 15 16:31:14 2008
From: krcoombes at mdacc.tmc.edu (Kevin R. Coombes)
Date: Mon, 15 Dec 2008 09:31:14 -0600
Subject: [Rd] package development
In-Reply-To: <18757.28023.55046.821105@ron.nulle.part>
References: <200812112304.mBBN4stJ008607@rocky.mayo.edu>	<4941A995.1040409@stats.uwo.ca>	<49427147.5070204@bank-banque-canada.ca>	<e8e755250812120747x241cde78y65e12b3a27ea518a@mail.gmail.com>	<49428BB7.6030406@bank-banque-canada.ca>
	<18757.28023.55046.821105@ron.nulle.part>
Message-ID: <49467842.6090004@mdacc.tmc.edu>

Hi,

Terry Therneau's question about package development reminded me of a 
different issue. I maintain several packages along with a repository for 
them at "http://bioinformatics.mdanderson.org/OOMPA/". Several people 
are working on adding features or testing the packages. So, I often want 
to have both the latest official release and the currently testable 
build of the package available in the repository. I tried putting both 
versions in the same repository, but this leads to a problem for some of 
the testers, who are not familiar with the intricacies of building 
packages. (Thus, I cannot just tell them to get the source tarball and 
compile it; they will have no clue as to what I am talking about. And 
their Windows machines will not have the required tools installed in any 
event.)

The underlying problem is that when you run the command
 >  install.packages(repos="http://bioinformatics.mdanderson.org/OOMPA")
inside the R Windows GUI, the selection box that appears only lists the 
name of the package, _not_ the version number. Thus, the testers cannot 
tell which of two packages with the same name should be installed.

Is there any way around this problem other than to maintain two 
different repositories?

Thanks in advance,
	Kevin



[Rd] package development
Kevin R. Coombes