The R Project SVN R

Rev

Rev 61160 | Rev 65966 | Go to most recent revision | Show entire file | Ignore whitespace | Details | Blame | Last modification | View Log | RSS feed

Rev 61160 Rev 61433
Line 56... Line 56...
56
\details{
56
\details{
57
  \code{write_PACKAGES} scans the named directory for R packages,
57
  \code{write_PACKAGES} scans the named directory for R packages,
58
  extracts information from each package's \file{DESCRIPTION} file, and
58
  extracts information from each package's \file{DESCRIPTION} file, and
59
  writes this information into the \file{PACKAGES} and
59
  writes this information into the \file{PACKAGES} and
60
  \file{PACKAGES.gz} files.
60
  \file{PACKAGES.gz} files.
61
  
61
 
62
  Including non-latest versions of packages is only useful if they have
62
  Including non-latest versions of packages is only useful if they have
63
  less constraining version requirements, so for example
63
  less constraining version requirements, so for example
64
  \code{latestOnly = FALSE} could be used for a source repository when
64
  \code{latestOnly = FALSE} could be used for a source repository when
65
  \samp{foo_1.0} depends on \samp{R >= 2.15.0} but \samp{foo_0.9} is
65
  \samp{foo_1.0} depends on \samp{R >= 2.15.0} but \samp{foo_0.9} is
66
  available which depends on \samp{R >= 2.11.0}.
66
  available which depends on \samp{R >= 2.11.0}.
Line 72... Line 72...
72
  Support for more general file names (e.g. other types of compression)
72
  Support for more general file names (e.g. other types of compression)
73
  \emph{via} a \code{"File"} field in the \file{PACKAGES} file was added
73
  \emph{via} a \code{"File"} field in the \file{PACKAGES} file was added
74
  in \R 2.10.0 and can be used by \code{\link{download.packages}}.  If
74
  in \R 2.10.0 and can be used by \code{\link{download.packages}}.  If
75
  the file names are not of the standard form, use
75
  the file names are not of the standard form, use
76
  \code{addFiles = TRUE}.
76
  \code{addFiles = TRUE}.
77
  
77
 
78
  \code{type = "win.binary"} uses \code{\link{unz}} connections to read
78
  \code{type = "win.binary"} uses \code{\link{unz}} connections to read
79
  all \file{DESCRIPTION} files contained in the (zipped) binary packages
79
  all \file{DESCRIPTION} files contained in the (zipped) binary packages
80
  for Windows in the given directory \code{dir}, and builds files
80
  for Windows in the given directory \code{dir}, and builds files
81
  \file{PACKAGES} and \file{PACKAGES.gz} files from this information.
81
  \file{PACKAGES} and \file{PACKAGES.gz} files from this information.
82
}
82
}
Line 86... Line 86...
86
  packages were found and no files were written.
86
  packages were found and no files were written.
87
}
87
}
88
\note{
88
\note{
89
  Processing \file{.tar.gz} archives to extract the \file{DESCRIPTION}
89
  Processing \file{.tar.gz} archives to extract the \file{DESCRIPTION}
90
  files is quite slow.
90
  files is quite slow.
91
  
91
 
92
  This function can be useful on other OSes to prepare a repository to
92
  This function can be useful on other OSes to prepare a repository to
93
  be accessed by Windows machines, so \code{type = "win.binary"} should
93
  be accessed by Windows machines, so \code{type = "win.binary"} should
94
  work on all OSes.
94
  work on all OSes.
95
}
95
}
96
\author{
96
\author{