similar to: Loading text file from data folder of package

Displaying 20 results from an estimated 30000 matches similar to: "Loading text file from data folder of package"

2004 Mar 15
1
R v1.9.0 alpha w/ Rtools: gzip problem
Hi, Gordon Smyth brought the following problem to my attention. PROBLEM/"BUG": Using R v1.9.0 alpha for Windows and the latest Rtools from Brian Ripley you get the following problem trying to R CMD build a package (or a bundle); >R CMD build R.basic * checking for file 'R.basic/DESCRIPTION' ... OK * preparing 'R.basic': * checking whether 'INDEX' is
2005 May 09
1
can't build packages anymore...
R developers, I've been happily building packages, under windows, for some time now and upgraded to R 2.1.0 and now when I attempt to build a package, I get the following errors... C:\conifers>rcmd build Rconifers * checking for file 'Rconifers/DESCRIPTION' ... OK * preparing 'Rconifers': * checking DESCRIPTION meta-information ... OK * cleaning src * checking whether
2007 Oct 04
1
Problem with .libPaths & Rterm.exe (under Vista)
Dear list, I?m using R embedded in another program (coded in tcl/tk) under Windows Vista. In this context I don?t launch Rgui.exe but rather Rtem.exe. Now I have a problem finding libraries not specifically installed as administrator (and which are not in the path ?program files? but in Contacts\Documents of the current user). To be precise, the user launching my tcl/tk program can?t find
2007 May 14
3
RFC: allow packages to advertise vignettes on Windows
Hello, The vignette concept, which started in Bioconductor, seems to be catching on. They are supported by R CMD build/check and documented in the Writing R Extensions manual. I think vignettes are a fantastic way to introduce new users to a package. However, getting new users to realize that a vignette is available can be challenging. For some time now, we have had a function in Biobase that
2013 May 02
1
R CMD building SPEEDY
Hello every one: I get following warning when building my R package with R-3.0.0. building 'SPEEDY.tar.gz' Warning in utils::tar(filepath, pkgname, compression = "gzip", compression_level = 9L, : number of items to replace is not a multiple of replacement length thanks Michael I have no idea for this, can you help me. Best regard
2012 Apr 17
2
Error with Rcmd check library --as-cran
Hello all, I was checking the newest update of my library before submitting it to CRAN, using R 2.15.0 and Rtools for Windows 215 using Rcmd in the Command Prompt, on my x64 Windows7 laptop. I recently heard that for checking packages for CRAN submission one should use the option --as-cran; previously I was submitting packages, so I was trying that for the first time. The check proceeds fine
2002 May 02
3
Building own packages on Windows 2000!
Hi! I encountered some things trying to build own packages under Windows 2000 for which i found no answer in the documentation. First. 1. I do not found the rcmd.exe in the bin directory of R_HOME. I installed R using the setup.exe 2. I updated the R intatllation with one of the zip files. (rw1041sp.zip) now i had the rcmd.exe in the bin. 3. I do not found any hint in the docu that perl is
2012 May 02
1
--as-cran error
Dear List, While using the --as-cran option for checking one of my packages: R CMD check --as-cran hydroGOF_0.3-3.tar.gz I got the following error message: pkgname <- "hydroGOF" > source(file.path(R.home("share"), "R", "examples-header.R")) > options(warn = 1) > library('hydroGOF') Error in loadNamespace(i[[1L]], c(lib.loc,
2011 Nov 18
2
cannot set the path to installed R packages when building a package vignette
Dear colleagues, I am having issues trying to build a R package I recently wrote. I am using R 2.14.0 and my package depends on another package called aod. Running: R CMD Sweave vignette.Rnw is perfectly fine and the vignette compiles properly. but when I use R CMD build mypackage to build the tar.gz I get the following error: * installing the package to re-build vignettes * creating
2007 Oct 02
0
patch: allow R CMD build exclude patterns to match symlinks
The following is a patch (svn diff) for the R CMD build script that calculates exclude patterns after the tar/untar step rather than before. The perl find() function, used in the calculation of the exclude patterns, ignores symlinks, which meant that directory symlinks were not considered for exclusion. Since the tar/untar step resolves (copies) symlinks, this works around that limitation.
2004 Apr 27
1
'R CMD build' fails when there are spaces in the path (PR#6830)
Full_Name: Byron Ellis Version: R 1.9.0 (and 2.0.0) OS: Linux (Redhat Fedora Core) Submission from: (NULL) (140.247.241.197) It appears that `R CMD build` cannot handle spaces in the path when building packages for distribution. For instance: [ellis@net-78815 ~/Bayesian Networks]$ R CMD build bnsl * checking for file 'bnsl/DESCRIPTION' ... OK * preparing 'bnsl': * cleaning src *
2025 Jan 16
1
Depends: R (>= 4.1) for packages that use |> and \(...)
Hello R-devel, Approximately [*] the following CRAN packages make use of the pipe syntax in their source code or examples without depending on R >= 4.1: [1] "biplotEZ" "CaseBasedReasoning" "collinear" [4] "cubble" "disk.frame" "duckdbfs" [7] "eia" "feltr"
2025 Jan 16
1
Depends: R (>= 4.1) for packages that use |> and \(...)
Thanks for looking into this and the patch. FWIW, there's an open PR18105 - "R CMD build: Add dependency on R >= 4.1.0 if code uses pipe symbol |>" for this (https://bugs.r-project.org/show_bug.cgi?id=18105). /Henrik On Thu, Jan 16, 2025 at 3:42?AM Ivan Krylov via R-devel <r-devel at r-project.org> wrote: > > Hello R-devel, > > Approximately [*] the
2025 May 15
1
customizing library locations for R in ubuntu
I did some googling and then ran: > bspm::shadowed_packages() ???? Package???????????????? LibPath Version?????? Shadow.LibPath Shadow.Version Shadow.Newer bspm????bspm /usr/lib/R/site-library?? 0.5.7 /home/ravi/rvi/Rlib??????????0.5.7????????FALSE I have a copy of bspm in the /usr/lib/R/site-library location as well, although that is not the 1st in my list of libPaths. This got included
2025 Jan 17
1
Depends: R (>= 4.1) for packages that use |> and \(...)
>>>>> Henrik Bengtsson writes: Thanks. Will take a look ... Best -k > Thanks for looking into this and the patch. FWIW, there's an open > PR18105 - "R CMD build: Add dependency on R >= 4.1.0 if code uses pipe > symbol |>" for this > (https://bugs.r-project.org/show_bug.cgi?id=18105). > /Henrik > On Thu, Jan 16, 2025 at 3:42?AM Ivan Krylov
2025 Jan 19
1
Depends: R (>= 4.1) for packages that use |> and \(...)
>>>>> Kurt Hornik writes: Oh dear. Using a variant of Ivan's code, I seem to find 728 (!!!) CRAN packages which are missing their R >= 4.1 dependency. So clearly we need to do more about this than teach R CMD build to add the dependency ... Best -k >>>>> Henrik Bengtsson writes: > Thanks. Will take a look ... > Best > -k >> Thanks for
2015 Jul 09
4
R CMD build failure
I have a local library 'dart' that imports "httr". It has routines that access central patient data such as birth date, so it is heavily used locally but of no interest to anyone else. The httr library (and 300 others) are in a shared directory, referenced by everyone in the biostatistics group via adding this location to the .libPaths in their default .Rprofile.
2025 Jan 22
1
Depends: R (>= 4.1) for packages that use |> and \(...)
>>>>> Kurt Hornik writes: I just committed c8761[2-4] to the trunk which adds an internal utility for finding package code using the pipe or function shorthand, teaches R CMD build to add a dependency on R >= 4.1.0 as necessary, and teaches R CMD check to NOTE a missing dependency on R >= 4.1.0, based on Ivan's code. Currently, we seem to have about 1149 packages on
2010 Aug 21
1
R CMD build --binary without option --use-zip-data
Hello, When I run R CMD build --binary pkgname I get * checking for file 'pkgname/DESCRIPTION' ... OK * preparing 'pkgname': * checking DESCRIPTION meta-information ... OK * cleaning src * removing junk files * checking for LF line-endings in source and make files * checking for empty or unneeded directories * building binary distribution * installing *source* package
2009 Mar 31
4
what is the preferred method to create a package local variable?
for the moment, I'm using: .onAttach <- function(libname, pkgname) { .bbg.db.conn <<- dbConnect(dbDriver("PostgreSQL"), user="blah","blah") } .onUnload <- function(libpath) { dbDisconnect(.bbg.db.conn) } which results in a hidden global variable in the global environment. I would prefer to make the assignment only in the package namespace.