\HeaderA{getReposEntry}{A function to retrieve a ReposEntry object from a repository}{getReposEntry}
\keyword{utilities}{getReposEntry}
\begin{Description}\relax
Will retrieve repository information from a specified repository, and
pass back a ReposEntry object containing this information.
\end{Description}
\begin{Usage}
\begin{verbatim}
getReposEntry(repURL, repFile = "replisting", rddFile =
"repdatadesc.rda", rtFile = "repThemes.rda", method="auto") 
\end{verbatim}
\end{Usage}
\begin{Arguments}
\begin{ldescription}
\item[\code{repURL}] URL of the repository
\item[\code{repFile}] Name of the remote replisting file
\item[\code{rddFile}] Name of the remote dataframe RDA file.
\item[\code{rtFile}] Name of the remote theme RDA file.
\item[\code{method}] Method used for file downloads.  See \code{download.file}
\end{ldescription}
\end{Arguments}
\begin{Details}\relax
More often then not, it will be more convenient for a user interacting
with an \R{} session to use the function \code{\LinkA{repositories}{repositories}}.

The symbolic names used to reference the URLs in the
\code{repositories2} option can also be used for the \code{repURL}
argument.  

The latter three options should be left to the defaults in almost all
cases.

The remote replisting and (if available) repdatadesc.rda
and repThemes.rda files are downloaded from the specified repository
and combined to form a ReposEntry object.
\end{Details}
\begin{Value}
The constructed ReposEntry object, or NULL on failure.
\end{Value}
\begin{Author}\relax
Jeff Gentry
\end{Author}
\begin{SeeAlso}\relax
\code{\LinkA{repositories}{repositories}}, \code{\LinkA{ReposEntry-class}{ReposEntry.Rdash.class}}
\end{SeeAlso}
\begin{Examples}
\begin{ExampleCode}
  z <- getReposEntry("http://www.bioconductor.org/repository/sample/package")
  z

  a <- getReposEntry("BIOCcdf")
  repURL(a)
  a
\end{ExampleCode}
\end{Examples}