similar to: dos-style line endings in .Rbuildignore result in files not being excluded

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

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,

I've changed to Mercurial for my working copies of survival for a number or resons not relevant to this post. When I do R CMD check, I get some warnings about certain files in the .hg directory with odd names. I've added the following 2 lines to my .Rbuildignore file without effect ^\.hg$ ^\.hg.* I'm not a Perl user so perhaps I'm reading the help page wrong. Any pointers? This

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

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

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

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.

Full_Name: Ben Goodrich Version: 2.6.1 OS: Debian Submission from: (NULL) (128.103.222.166) bzr is another version control system and adds a .bzr folder to the top-level directory of a package, similar to .svn and .git for subversion and git respectively. However, while R CMD build removes directories called .svn, .git, and some others, it does not remove .bzr . As a result, the .bzr folder is

Hi, I use rsync 3.0.2 for daily incremental backups: rsync -aAzHRxby -f '. -' --numeric-ids --delete-during --delete-excluded \ --suffix='' --backup-dir=$BACKUP_ROOT/$BACKUP_HOST/${TODAY} \ ${DESTINATION}$BACKUP_ROOT/$BACKUP_HOST/current <<< $EXCLUDE_PATTERNS Sometimes I add a new item to $EXCLUDE_PATTERNS but then the excluded files are backed up in

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'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

Hi, In my package RGtk2, there's a directory called 'src/RGtk2' that contains, like all the other directories in the package, a '.svn' directory. It seems that R CMD build is somehow missing that one '.svn' in 'src/RGtk2', even though it excludes all the other instances of '.svn'. I've tried putting 'src/RGtk2/.svn' into the .Rbuildignore,

Writing R Extensions mentions that a package developer can provide a Makefile, but gives very little information about what should be in it. It says there must be a clean target, and later on there's mention of $(SHLIB): $(OBJECTS) $(SHLIB_LINK) -o $@ $(OBJECTS) $(ALL_LIBS) (in the F95 discussion). What should a Makefile provide, and what can it assume? In other words,

On posix systems, invoking R with arguments containing shell word delimiters (like space) doesn't currently work: bash-2.05b$ ./R -f "/path/to/script with spaces.R" Fatal error: cannot open file '/path/to/script': No such file or directory The attached patch, built against the devel snapshot of 2008-09-20, attempts to fix this problem. In R.sh.in and BATCH, it

Noted Duncan and TRUE... I cannot do more immediately unfortunately, that is always the issue of asking a last minute panic attack question before teaching a course involving the package... I do have /doc in my .Rbuildignore for reasons I can no longer remember... I will dig and create a MRE/reprex. The students will download heavy packages, but they probably won't notice. *Apologies* In the

In R 2.8. I get the following warning when checking my package: * checking for executable files ... WARNING Found the following executable file(s): .git/objects/00/12947a4bb4379fb0c3bed740314a9f4ac72331 .git/objects/00/21fac22a57a1567389ed34a9dc4f465c6cfd01 .git/objects/00/29da5c289489fdb2249e19f4b165ff5b37b3e6 .git/objects/00/36ad7f586eeac250e6609a1bf938e545101cb0 ... (for about 300

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

That is more or less what I had been doing for a long time (having both NEWS.md and NEWS), but decided not to do it any more last year. In fact, you can easily convert NEWS.md to a NEWS file that R's news() can understand, e.g. https://github.com/yihui/knitr/blob/947ad5fc94/Makefile#L8-L10 (if your NEWS.md is like this https://raw.githubusercontent.com/yihui/knitr/947ad5fc94/NEWS.md) I

Is it possible to consider adding .emacs.desktop and .emacs.desktop.lock to files ignored by R CMD build? Thanks, Georgi -- Dr Georgi Boshnakov tel: (+44) (0)161 306 3684 School of Mathematics fax: (+44) (0)161 306 3669 Alan Turing Building 1.125 The University of Manchester email: Georgi.Boshnakov at manchester.ac.uk Oxford Road Manchester M13 9PL UK

Git is a source code management system like CVS, svn, arch, and others. It would be nice to add exclude support to R CMD build and INSTALL so that the .git subdir of an R package is handled appropriately. Here is a possible patch: diff --git a/src/scripts/INSTALL.in b/src/scripts/INSTALL.in index 75da9db..09e5ab5 100644 --- a/src/scripts/INSTALL.in +++ b/src/scripts/INSTALL.in @@ -863,7