-
Notifications
You must be signed in to change notification settings - Fork 1
/
HOW_TO_UPDATE.txt
49 lines (32 loc) · 1.74 KB
/
HOW_TO_UPDATE.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
NOTES ON BLOXSOM UPDATES
Each annual R release means manual intervention is needed.
1. Edit blosxom/diffNEWS.R to add the new release branch. E.g. for the 3.2 branch,
I added the lines
NEWS32done <- list("2015-03-08", 68017)
NEWS32done <- dailyDiffNEWS("~/R/R-3-2-branch/doc/NEWS.Rd", NEWS32done,
dir="~/blosxom/data/R-3-2-branch/NEWS",prefix="n")
save(NEWSdone,
NEWS31done,
NEWS32done,
file="~/blosxom/start.RData")
in the obvious places. Delete the 2nd previous release, i.e. 3-0-branch related
files in this case.
2. Get a copy of the source for the new branch in the R directory. Easiest is probably
to copy another branch and use svn switch. E.g.
cd ~/R
cp -r R-3-1-branch/ R-3-2-branch
cd R-3-2-branch
svn switch https://svn.r-project.org/R/branches/R-3-2-branch
3. Make sure rJava is installed in the current R:
~/R/build/bin/R
> install.packages("rJava")
4. Create the new directory to hold the news:
mkdir -p ~/blosxom/data/R-3-2-branch/NEWS
5. Run the diffNEWS.R script and make sure it worked:
~/R/build/bin/Rscript /home/murdoch/blosxom/diffNEWS.R
6. In the developer.r-project.org web page (stored at
/www/rdevel/htdocs/RSSfeeds.html), add the new branch, e.g.
<tr><td class=firstcolumn><b>R-3-2-branch</b></td>
<td class=cellinside> <a href="http://developer.r-project.org/blosxom.cgi/R-3-2-branch/NEWS">http://developer.r-project.org/blosxom.cgi/R-3-2-branch/NEWS</a> </td>
<td class=cellinside> <a href="http://developer.r-project.org/blosxom.cgi/R-3-2-branch/NEWS/index.rss"><img src="feed-icon-14x14.png"></a> </td>
</tr>