Tag Archives: Charlie Sharpsteen

pgfSweave now on CRAN

At long last pgfSweave has finally made its way to CRAN.


The pgfSweave R package is about speed and style of graphics. For speed, the package provides capabilities for “caching” graphics generated with Sweave on top of the caching funcitonality of cacheSweave. For style the pgfSweave package facilitates the integration of R graphics with LaTeX reports through the tikzDevice package and eps2pgf utility. With these tools, figure labels are converted to LaTeX strings so they match the style of the document and the full range of LaTeX math symbols/equations are available.

The backbone of pgfSweave is a a new driver for Sweave (pgfSweaveDriver). The driver provides new chunk options tikz, pgf and external on top of the cache option provided by cacheSweave.

This package started as a fork (hack) of cacheSweave to suit our own narrow purposes and has since become a valuable tool for much of our own work. We hope you will find it useful as well.

-Cameron Bracken and Charlie Sharpsteen

Using Git with R-Forge OR Adding an local Git branch to track an Subversion Repo

These instructions were originally from instructions from my friend Charlie.

I really like to use Github but R-Forge has alot of nice features for package development, so why not get the best of both worlds.

Say you have a git repo (with an R package or something else) but want to create a local brach which tracks an svn repo (from R-Forge) such that you can merge changes from your git repo in and then commit them to svn. First use the following command to grab the current svn:

cd my-r-package
git svn clone svn+ssh://developername@svn.r-forge.r-project.org/svnroot/my-r-package .

This will create a new git repository that is a mirror of whatever svn repo you pointed at. This may take a while if you have a big existing svn repo.

If you want to add a svn bound branch to an existing git repo:

Edit .git/config and add the following:

[svn-remote "r-forge"]
  url = path/or/url/to/svn/repository
  fetch = :refs/remotes/r-forge-svn

Once you’ve done this, you have created an entry for a new git remote server- fetch the status and history of it’s branches using the following:

git svn fetch r-forge

If this command is successful, git branch -a should show:


In the list of available branches. This branch is a remote branch- to make a local copy, do the following:

git checkout r-forge-svn
git checkout -b r-forge-svn-local

Now you have a local branch which is bound to the svn server- once again straight up adding/removing/moving files in this branch should work fine. It’s merging that gets you into trouble.

How to merge between a git branch and a git-svn branch

The point is that you don’t want git infecting your subversion repository with any of its awesomeness. Exposure to the kind of concentrated badass possessed by git causes poor SVN’s head to pop. So, the merge must be done as follows:

git checkout r-forge-svn-local
git merge –squash branch-to-merge-in

The --squash option tells git to leave out any info about what happened during the merge and act like it just mashed a bunch of files into your svn branch using copy commands.

Once you’ve added/copied/moved/squashmerged new files into your local svn branch- do the following to push the changes to the svn repo:

git commit -a               (Commit changes to your git repo as normal.)
git svn dcommit           (This will form each git commit into a svn commit and send it to the svn repo)

To pull changes from the svn repo run the following:

git svn rebase