similar to: tools:: extracting pkg dependencies from DCF

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 R-Users, I'm trying to setup a personal repository for a few packages I'm working on. I am on R-Forge but I still need to have various versions of my package that R-Forge does not build (for R 2.8.1 for example). So I followed the instructions in this document: Hhttp:// cran.r-project.org/doc/manuals/R-admin.html#Setting-up-a-package-repository and used this function as

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

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

I set up a local repo for testing packages. My packages are not showing up from the repository when viewed by Linux clients. I suspect this is a web administrator/firewall issue, but it could be I created the repo wrongly. I am supposed to run write_PACKAGES separately in each R-version folder. Right? Maybe other novices can use these scripts, if they are not wrong :) Here's the file

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)

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

Hi, read.dcf() can modify the locale variable LC_CTYPE, and here is a minimal example: > Sys.getlocale('LC_CTYPE') [1] "en_US.UTF-8" > read.dcf(textConnection('a: b'), all = TRUE) a 1 b > Sys.getlocale('LC_CTYPE') [1] "C" After diagnosing the problem, it seems the on.exit() call in read.dcf() is the culprit:

Hi, on all my systems update.packages() and install.packages() fails now. I get the following message: root at orca:/root(28)# R R version 2.10.1 (2009-12-14) Copyright (C) 2009 The R Foundation for Statistical Computing ISBN 3-900051-07-0 R is free software and comes with ABSOLUTELY NO WARRANTY. You are welcome to redistribute it under certain conditions. Type 'license()' or

I'm seeing a segfault on x86_64 Linux with the following code: desc = read.dcf("BAD") con = gzfile("test.gz", "wt") write.dcf(desc, file=con) close(con) where BAD has a long field (see below for example). The crash happens inside dummy_vfprintf. I think the issue is that the va_list ap is modified by the first vsnprintf call

Hi everyone, I've followed the instructions from R-Admin Section 6.6 for creating a local repository. I've modified my Rprofile.site file to add the local repository to my repos, but I haven't been able to successfully install my package from the repo. Here's the code that I've run. ################################## sessionInfo() getOption("repos")

Hi guys I think there's a high chance this is a bug. But I can't rule out that I can be blamed for this. I've posted this to bugzilla (#15092). Then I read that I probably should have posted it to R-develop first. Sorry for doing this in the wrong order. I've set up a local repo on my local drive (happens to be mapped to L:/). It has the following structure (as per

Was looking at what was output for <pkgname>-package.Rd and wondered if any there was any means (via macro, etc) to merge some of the same information with a template for my package manpage? As much (all?) of the generated information was already provided in the DESCRIPTION, I'd prefer not to have to update the information in multiple places. I'm thinking here that I could provide a

Hi all, The write_PACKAGES function has a 'fields' argument that allows a user generating a PACKAGES file to specify additional fields to include. For symmetry, it would be nice for the available.packages function to be able to read those extra fields when specified. Similarly, it would be useful for installed.packages to have a 'fields' argument. This would allow a user to

Hi, After updating to R-3.0 beta r62328, I get the following: > install.packages("Biobase", type="source", repos="http://george2/BBS/2.12/bioc") Error in do.call(op, list(v_c, v_t[[op]])) : could not find function "R (>=2.15.1)" The problem can be fixed by adding a space after >= in the offending package's DESCRIPTION file and re-generating

I try to update R packages via my local repository. I put all R packages in g:/myFolder/myRepository, I do like > library(tools) > write_PACKAGES("g:/myFolder/myRepository") > options(repos=c(LocalR="file://g:/myFolder/myRepository")) > getOption("repos") LocalR "file://g:/myFolder/myRepository" >

Dear all, I?m working as a data scientist in a major tech company. I have been using R for almost 20 years now and there?s one issue that?s been bugging me of late. I apologize in advance if this has been discussed before. R has traditionally been used for running short scripts or data analysis notebooks, but there?s recently been a growing interest in developing full applications in the

Hi all, I have recently been researching how available.packages and install.packages filter packages from repositories with additional fields in their PACKAGES file. Currently there are some default filters, but users (and R admins) can set up their own filters by passing a list to the fields argument or adding them to the "available_packages_filters" option. But if the fields used by