similar to: Splus-specific entries in pkg/DESCRIPTION files

Currently system.file(package="no such pkg","no","such","file") silently returns the empty string, "", if said file doesn't exist. This forces the caller to check for "" or risk getting a mysterious error message from a function requiring a file name. E.g., > read.dcf(system.file(package="no such

Dear R devs, I would like to raise a request for a simple helper function. Utility function to extract package dependencies from DESCRIPTION file. I do think that tools package is better place, for such a fundamental functionality, than community packages. tools pkg seems perfect fit (having already great function write_PACKAGES). Functionality I am asking for is already in R svn repository

Thank you Gabriel, Just for future readers. Below is a base R way to address this common problem, as instructed by you (+stopifnot to suppress print). Rscript -e 'stopifnot(file.copy("DESCRIPTION", file.path(tdir<-tempdir(), "PACKAGES"))); db<-available.packages(paste0("file://", tdir));

Dear Jan, Similar functionality is available in devtools::dev_package_deps() Best regards, ir. Thierry Onkelinx Instituut voor natuur- en bosonderzoek / Research Institute for Nature and Forest team Biometrie & Kwaliteitszorg / team Biometrics & Quality Assurance Kliniekstraat 25 1070 Anderlecht Belgium To call in the statistician after the experiment is done may be no more than asking

Dear Jan, It is unavoidable to have OS and R dependencies for devtools. The building process for packages is both OS and R dependent, so devtools has to be too according to my understanding. Cheers Joris On 14 Jun 2016 18:56, "Jan G?recki" <J.Gorecki at wit.edu.pl> wrote: Hi Thierry, I'm perfectly aware of it. Any idea when devtools would be shipped as a base R package, or

I agree that the utils package needs some improvements related to this, and hope to make them eventually. This type of feedback is very helpful. Thanks, Michael On Thu, Jun 16, 2016 at 1:42 AM, Jan G?recki <J.Gorecki at wit.edu.pl> wrote: > Dear Joris, > > So it does looks like the proposed function makes a lot sense then, isn't it? > > Cheers, > Jan > > On 16

Hi Michael, Are you willing to accept patch for this? I'm already using this and few related functions for a while, it plays well. I could wrap it as patch to utils, or tools? Best, Jan On 16 June 2016 at 14:00, Michael Lawrence <lawrence.michael at gene.com> wrote: > I agree that the utils package needs some improvements related to > this, and hope to make them eventually. This

Dear R-devel list, I would like to enquire about the existence of blank lines in the DESCRIPTION file. Testing different possibilities with tools:::.read_description suggests that starting or ending with blank lines is acceptable while blank lines in the middle of the file get caught by out <- tryCatch(read.dcf(dfile, keep.white = .keep_white_description_fields), error = function(e)

Dear Joris, So it does looks like the proposed function makes a lot sense then, isn't it? Cheers, Jan On 16 June 2016 at 08:37, Joris Meys <jorismeys at gmail.com> wrote: > Dear Jan, > > It is unavoidable to have OS and R dependencies for devtools. The building > process for packages is both OS and R dependent, so devtools has to be too > according to my understanding.

Hi all, Packages tools and utils have a lot of useful stuff for R developers. I find one task still not as straightforward as it could. Simply to extract dependencies of a package from DESCRIPTION file (before it is even installed to library). This would be valuable in automation of CI setup in a more meta-data driven way. The simple function below, I know it is short and simple, but having it to

Full_Name: Bill Dunlap Version: 2.5.0 OS: Red Hat Enterprise Linux WS release 3 (Taroon Update 6) Submission from: (NULL) (24.17.60.30) If you read a dcf file with read.dcf(file,fields=c("Field",...)) and the file does not contain the desired field "Field", read.dcf puts a character NA for that entry in its output matrix. If you then call write.dcf, passing it the output of

On Mon, Sep 21, 2015 at 2:48 PM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > On 21/09/2015 4:50 PM, Herv? Pag?s wrote: >> Hi, >> >> Note that one significant change to read.dcf() that happened since R >> 3.0.2 is the addition of support for arbitrary long lines (commit >> 63281), which never worked: >> >> dcf <- paste(c("aa:

BIll, Thanks. I am seeing some problems here, for example when all the fields are missing, or all the fields in a row are missing. I've fixes for those, and will commit to R-devel shortly. On Tue, 17 Jul 2007, bill at insightful.com wrote: > Full_Name: Bill Dunlap > Version: 2.5.0 > OS: Red Hat Enterprise Linux WS release 3 (Taroon Update 6) > Submission from: (NULL)

On 21/09/2015 10:20 PM, Vinh Nguyen wrote: > On Mon, Sep 21, 2015 at 2:48 PM, Duncan Murdoch > <murdoch.duncan at gmail.com> wrote: >> On 21/09/2015 4:50 PM, Herv? Pag?s wrote: >>> Hi, >>> >>> Note that one significant change to read.dcf() that happened since R >>> 3.0.2 is the addition of support for arbitrary long lines (commit >>>

On 21/09/2015 4:50 PM, Herv? Pag?s wrote: > Hi, > > Note that one significant change to read.dcf() that happened since R > 3.0.2 is the addition of support for arbitrary long lines (commit > 63281), which never worked: > > dcf <- paste(c("aa: ", rep(letters, length.out=10000)), collapse="") > writeLines(dcf, "test.dcf") >

Hi, I am new to R and I'm looking to perform some method comparison analysis and would be grateful for some help regarding package installation. There is a package 'MethComp' that I want to use (http://staff.pubhealth.ku.dk/~bxc/MethComp/Courses/Sthm.2007/.) Unfortunately I am unable to install it. I have tried numerous approaches but to no avail. this is the first time I have tried to

The change in r42731 eliminating the final blank line when writing DCF files changes the way 'append' can be used in 'write.dcf' and I was wondering if this is intentional. Basically, I want to write a data frame to DCF format one row at a time, so I make use of repeated calls to 'write.dcf(append = TRUE)'. However, in R 2.6.0RC the resulting DCF file is not formatted

Hi, Note that one significant change to read.dcf() that happened since R 3.0.2 is the addition of support for arbitrary long lines (commit 63281), which never worked: dcf <- paste(c("aa: ", rep(letters, length.out=10000)), collapse="") writeLines(dcf, "test.dcf") nchar(read.dcf("test.dcf")) # aa # [1,] 8186 The culprit being line

Full_Name: charles blundell Version: 2.7.0 OS: Debian GNU/Linux Submission from: (NULL) (217.37.73.202) The Debian Policy Manual says concerning lines in a Description field: * Those containing a space, a full stop and some more characters. These are for future expansion. Do not use them. (section 5.6.13, http://www.debian.org/doc/debian-policy/ch-controlfields.html) But for example: >

I don't know if this is a bug per se, but an undesired behavior in read.dcf. read.dcf takes a file argument and passes it to gzfile if it's a character: if (is.character(file)) { file <- gzfile(file) on.exit(close(file)) } This gzfile connection is passed to readLines (line #39): lines <- readLines(file) If no newline is at the end of the file, readLines