similar to: Rbuildignore and mercurial

I'm touching up changes to rpart and have a question with .Rbuildignore. Here is my file tmt1014% more .Rbuildignore test.local \.hg src/print_tree.c The source code included a module "print_tree.c", used for dubugging. Commented out calls to can be found here and there. I want to leave it in the source tree even though no submitted copy of rpart will use it. Even with the

Context: R2.15-0 on Ubuntu. 1. I get a WARNING from CMD check for "Package vignette(s) without corresponding PDF: In this case the vignettes directory had both the pdf and Rnw; do I need to move the pdf to inst/doc? I'm reluctant to add the pdf to the svn source on Rforge, per the usual rule that a code management system should not have both a primary source and a object

I was trying, on a Linux system, to get a .Rbuildignore file to work. After far too long, I found the problem was the <CR><NL> line endings in the .Rbuildignore file -- I had originally created it on a Windows system, and emacs in Ubuntu was politely hiding that fact from me. The patterns didn't work to exclude files because it was trying to match filenames to patterns like

I have some questions about building packages in Windows when using .Rbuildignore . The part of the process that is of interest here is the part that creates the source tree from the tree that contains the .Rbuildignore file. That is, the part of the process that does a build of the original tree creating a .tar.gz and then extracts this file into a source directory that can be used by check,

On Thu, 18 Nov 2004 00:38:47 +0000 (UTC), Gabor Grothendieck <ggrothendieck@myway.com> wrote : >DIFFERENCE BETWEEN USING .RBUILDIGNORE AND NOT > >The reason that the processing is different according to whether one >uses .Rbuildignore or not is that > R CMD build >takes the .Rbuildignore file into account but > R CMD install > R CMD check > R CMD build

Full_Name: David O. Nelson Version: 1.4.1 OS: solaris 2.7 Submission from: (NULL) (128.115.150.74) Putting patterns in .Rbuildignore has no effect when the tar being used is gnu tar (1.13) on solaris 2.7, whilst /usr/sbin/tar works perfectly. TO REPRODUCE: The current directory contains a source package directory ./mypkg... bimini.jgi-psf.org% echo >mypkg/foo bimini.jgi-psf.org% echo

Hi all, in particular package developers, I'm exploring using a version control system to keep better track of changes to the packages I maintain. I'm leaning towards git (although mercurial also looks good) but am not sure what is the best way to set up the repository. It seems I can't set the repository directly within the R package main directory, since it will be incompatible with

Hi all, in particular package developers, I'm exploring using a version control system to keep better track of changes to the packages I maintain. I'm leaning towards git (although mercurial also looks good) but am not sure what is the best way to set up the repository. It seems I can't set the repository directly within the R package main directory, since it will be incompatible with

The contents of .Rbuildignore seems to affect R CMD build but not R CMD check. I'm using R 2.4.0 on Debian. Is my understanding correct? And is there anything I can do about it? In my case, some of the excluded files contain references to other libraries, so linking fails under R CMD check. I realize I could add the library to the build (with Makevars, I guess), but I do not want to

R version 2.9.0 running on Centos (Red Hat linux). I have a pair of packages coxme and bdsmatrix. The latter is installed in my local library (I don't have permission for global install at work.) That is, it is in the location pointed to in R_LIBS_USER. In R, the command library(bdsmatrix) works fine. Coxme depends on bdsmatrix, in fact uses some cross-calls to it's C routines, which

When a package is built it is first moved to a temporary directory (lines 962-980 in build.R). However, this moves *all* files to the temporary directory, even those in Rbuildignore; only later (lines 997-1024) are Rbuildignore files excluded. The problem with this approach is that some files in the package directory may not be movable. On Windows at least, the full path name to a file must not

I have a local library with functions that interrogates an institution-specific web API, so is not of interest to anyone outside of Mayo. For some reason the R CMD INSTALL command fails. See below: Build the library, then install it. tmt-local2127% R CMD build dart * checking for file ?dart/DESCRIPTION? ... OK * preparing ?dart?: * checking DESCRIPTION meta-information ... OK * installing

I've made a package for which R CMD build isn't producing very satisfactory results. I'll get to the details in a moment. I wonder if it would make sense to have my own makefiles (which already exist and are doing quite a lot) produce the .tar.gz file ordinarily produced by R CMD build. As far as I can tell, R CMD build basically tars up of the project directory after running some

Gabor As someone trying to the rest of my team using Subversion (which I have used for a while, but more as a backup / record of changes), have you a neat / automated way of building a package from a subversion repository? Thanks David Jessop -------------------------- David Jessop Global Head of Quantitative Research UBS Investment Research +44 20 7567 9882 ----- Original Message -----

Hello all, I wish to learn a version control system for managing my R (data analysis) projects. I know of SVN and github, and wonder if there is any reason for which I should prefer the one over the other (or any other platform). An example for a reason could be if it will make it easier for me to later work with R-forge or CRAN or any other platform for R code distribution. Thanks, Tal

Re your point 3: Because you have managed to create a GitHub version of your repository that is not a fork of https://github.com/rforge/ecdat, but its own independent repository, contacting GitHub support might not be the right way forward. Note that https://github.com/rforge is simply a read-only mirror of the complete R-Forge repository (and at least to me it is unclear of whether GitHub itself

Mercurial(hg) Cheatsheet for Xen ================================ Written by Andrew Warfield, extended by Michael Fetterman and Ian Pratt June 29, 2005, extended by Grzegorz Milos 04 July 2005. Overview -------- The Xen project has moved from BitKeeper to Mercurial for source control. This note aims to provide a quick guide to getting up and running with the new tools as quickly as possible,

My docs say files ending in ~ are excluded by default from R CMD build. Doesn't look that way to me. I got them with 1.6.2 and 1.7.0. My documenation is 1.6.0 (that is, the one saying *~ is excluded). I have no .Rbuildignore of my own.

I've narrowed my scope problems with predict.coxph further. Here is a condensed example: fcall3 <- as.formula("time ~ age") dfun3 <- function(dcall) { fit <- lm(dcall, data=lung, model=FALSE) model.frame(fit) } dfun3(fcall3) The final call fails: it can't find 'dcall'. The relevant code in model.frame.lm is: env <- environment(formula$terms)

> Several changes in print.survfit, plot.survfit and seemingly in the structure > of ratetabels effect some of my syntax files. > Is there somewhere a documentation of these changes, besides the code itself? I agree, the Changelog.09 file is not as comprehensive as one would like. Specific comments: 1. The ratetables were recently changed to accomodate a new option. I thought