similar to: Customizing the package build process

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

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

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

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

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.

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

I'm having trouble un 'tar'ing the file ctest_0_9-3_tar.tar. When using the command "tar -xv" on a UNIX machine I get the "checksum error" message. When trying to use WinZip on a Win95 machine it gives an error reading the header. I'm downloading from the CRAN site at Carnegie Mellon. Could the file there be corrupted? Thanks for any help, and sorry if

I'm having trouble un 'tar'ing the file ctest_0_9-3_tar.tar. When using the command "tar -xv" on a UNIX machine I get the "checksum error" message. When trying to use WinZip on a Win95 machine it gives an error reading the header. I'm downloading from the CRAN site at Carnegie Mellon. Could the file there be corrupted? Thanks for any help, and sorry if

I am wanting to rsync over mac files to a freebsd 4.5 box, but have recently found out that rsync does not preserve resource forks, or creator types and maybe some other things. But, has anybody had any experience like this, would tar'ing the files and then rsync'ing that seem a worthwhile solution. There's a lot, so testing is going slowly. Thanks! Brad Lynch Info Sys Coordinator

When a generic (S4) has an argument with a default followed by ..., missing() doesn't seem to work if the method omits the ... --------------------Sample------------------------------- foo <- function(x, y=0, ...){ "you are very generic" } # no ... in function arguments setMethod("foo", signature="character", function(x, y=0){ if (missing(y))

When tar'ing up an ext3 filesystem on a 3ware RAID I have, I got the following errors in my system log: Apr 7 21:27:46 allo 3w-xxxx[957]: Drive error encountered on port 3 on controller ID:0. Check cables and drives for media errors. (0xa) Apr 7 21:27:46 allo kernel: 3w-xxxx: scsi0: Command failed: status = 0xc7, flags = 0x51, unit #0. Apr 7 21:27:58 allo last message repeated 3 times Apr

Fascinating. Or, well, not. Failing to use a method signature that is compatible with the generic is a no-no. So your bug seems to me to be outside the bounds of how R is supposed to be used. So don't do that. On April 17, 2024 4:25:38 PM PDT, "Boylan, Ross via R-help" <r-help at r-project.org> wrote: >When a generic (S4) has an argument with a default followed by ...,

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

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,

Trying to add SELinux support to my bitcoin package. Keep getting this on install: SELinux: Could not downgrade policy file /etc/selinux/targeted/policy/policy.29, searching for an older version. SELinux: Could not open policy file <= /etc/selinux/targeted/policy/policy.29: No such file or directory /sbin/load_policy: Can't load policy: No such file or directory

Hello All, Is it possible to serve up files anonymously via a folder of my choosing on demand? >From time to time where I work, we transfer large file heirarchies between co-workers and contractor workstations, and we've gotten away with tar'ing things up or using something like webfs (or Python -m SimpleHTTPServer) on one end and 'wget -r http://remote-server' on the the