Commit 11b21a9a authored by Radford Neal's avatar Radford Neal

update date in NEWS.Rd and INSTALL, tweak mods/README

parent b31e655a
......@@ -20,8 +20,8 @@ described below, and in the R-admin manual.
Configuring pqR
After uncompressing and unpacking the tar archive (with a command such
as "tar xf pqR-2014-10-18.tar.gz"), you should make a directory in
which to build pqR, such as "pqR-2014-10-18-myconfig". It is possible
as "tar xf pqR-2014-11-16.tar.gz"), you should make a directory in
which to build pqR, such as "pqR-2014-11-16-myconfig". It is possible
to instead build pqR in the source directory, but using a separate
directory is preferable, so that the source directory says clean, and
so that you can create more than one configuration if desired.
......@@ -31,7 +31,7 @@ You should then enter the build directory, and issue the command:
path-to-source-directory/configure
where "path-to-source-directory" is the path to the source directory,
perhaps something like "../pqR-2014-10-18".
perhaps something like "../pqR-2014-11-16".
The configure command will produce a lot of output regarding the
results of checks for various system facilities, and end (if
......
......@@ -6,7 +6,7 @@
\encoding{UTF-8}
\section{CHANGES IN VERSION RELEASED 2014-11-12}{
\section{CHANGES IN VERSION RELEASED 2014-11-16}{
\subsection{INTRODUCTION}{
......
......@@ -32,7 +32,9 @@ DD), with only the following changes:
build directory (with "C" locale), and then copying them to the
source directory (R-admin.html from doc/manual).
4) Concatenate all files in the "mods" directory into the file
4) Remove the file ".gitignore" (using "git rm", if you're using git).
5) Concatenate all files in the "mods" directory into the file
"MODS", as follows:
(cd mods; cat README; for i in [0-9]*; \
......@@ -40,8 +42,6 @@ DD), with only the following changes:
Then delete the "mods" directory (with "git rm -r" if using git).
5) Remove the file ".gitignore" (using "git rm", if you're using git).
The development branches that go into a release may be changed after
the release, with the new versions forming the basis for a later
release, but without the commits that produce these new versions being
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment