similar to: ~ files not excluded from build (PR#3071)

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

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

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

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

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

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,

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

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,

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

Hi all, I am new to this LLVM. I went through the documenation of LLVM but I didn't find any support for Multicore. Is there any such possibility where multicore architecture can be exploited using LLVM. Thanks Vijay -------------- next part -------------- An HTML attachment was scrubbed... URL:

And, I've found more. It turns out that even though the exclude directive is ignored for inbound data in rsyncd.conf, it is NOT ignored for the --delete option. I've seen this behavior occur when I've deleted a file from the sending side (client) that is inside a tree that's matched by the server-side (rsyncd) exclude directive. The deletion is ignored, as the documenation

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

Hi List; To create the symbolic link, I read in the documenation that I have to type this command: # ln -s /usr/src/'uname -r' /usr/src/linux-2.4 1) What it means by 'uname -r'? 2) Why I have to create such symbolic link to do pointing for the kernel? For what exctly will be used with asterisk? 3) What is the relation between creating such symbolic link and build directory? Any

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

It is so difficult ... Which FE? It need BE support? I didn't get it. 2010/8/4 vijay kumar <vijaygbvv at gmail.com> > Yeah OpenMP support. I read that it has a front end support but not the > back end. So are there any projects or teams looking at this issue. > > On Wed, Aug 4, 2010 at 7:24 AM, Liu <proljc at gmail.com> wrote: > >> Multicore? >> You

Dear all, I would like to find a linear regression model for a rather large dataset (27 independent variables). However, when I run lm the following error is reported: > out <- lm(Result ~ AppealA + AppealsB + AppealC + AppealD + AppealE + Apply + ApplyAmount + Aprove + Closecase + Decidelocally + Healthassessment + HealthassessmentHealth + Postponedecision + Propertyassessment +

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

Ok, my first complete swipe for the new docs (but still with old rdoc default output templates) can be seen at: http://www.mktec.com/dev_www/wxruby-docs/ Most of the classes/methods documentation came out fine, but I still need finetune because some methods don''t get documented at all, like methods in the classes Bitmap and Frame. Once I can get it so all things get documented