Re: [R-pkg-devel] author field in description problem

Uwe, Thanks. I was hoping that you would say that. Bill > On Feb 25, 2018, at 5:55 PM, Uwe Ligges > wrote: > > > > On 26.02.2018 00:39, William Revelle wrote: >> I did remove the author and maintainer fields. I have only the Authors@R >> field. However

Re: [R-pkg-devel] author field in description problem

I did remove the author and maintainer fields. I have only the Authors@R field. However it still throws that Note (in R 3.4.3) > On Feb 25, 2018, at 5:20 PM, Iñaki Úcar wrote: > > 2018-02-25 23:49 GMT+01:00 William Revelle : >> Hi, >> >> I am trying to

Re: [R-pkg-devel] author field in description problem

2018-02-25 23:49 GMT+01:00 William Revelle : > Hi, > > I am trying to take advantage of the Authors@R: field in my description file > for the psych package to add an ORCID address (as discussed in the R journal). > > When I R CMD check with R development on my Mac, or with win

[R-pkg-devel] author field in description problem

Hi, I am trying to take advantage of the Authors@R: field in my description file for the psych package to add an ORCID address (as discussed in the R journal). When I R CMD check with R development on my Mac, or with win builder it passes all checks. (R Under development (unstable) (2018-02-23

Re: [R-pkg-devel] stages of package loading

Am Sonntag, 25. Februar 2018, 12:38:35 CET schrieb meik michalke: > now i want to load A and B without X falsely informing me that they are > missing. i.e., it should be clear to X that A is available and currently > being loaded when X itself is loaded as the dependency of A. > > it seems

Re: [R-pkg-devel] [FORGED] Re: How to (conditionally) use an archived package (without Suggests)?

On 25 February 2018 at 16:45, Hugh Parsonage wrote: | Not to mention a drat repository you can just fork with a single click! Yes, very easy -- but marginally expensive as you get the content (ie drat code history) mirrored. If you're at ease with git you can do it all by hand too. We still

Re: [R-pkg-devel] [FORGED] Re: How to (conditionally) use an archived package (without Suggests)?

Not to mention a drat repository you can just fork with a single click! On Mon, 26 Feb 2018 at 3:25 am, Dirk Eddelbuettel wrote: > > On 25 February 2018 at 15:00, Marius Hofert wrote: > | okay, so (afaik) this is just a github repos which contains an exact > | copy of the github

Re: [R-pkg-devel] [FORGED] Re: How to (conditionally) use an archived package (without Suggests)?

On 25 February 2018 at 15:00, Marius Hofert wrote: | okay, so (afaik) this is just a github repos which contains an exact | copy of the github version of the problematic package (here: loon). I Be very careful with terminology here: -- "github repo" is to most people a source code repo --

Re: [R-pkg-devel] How to (conditionally) use an archived package (without Suggests)?

On 25 February 2018 at 14:20, meik michalke wrote: | Am Sonntag, 25. Februar 2018, 06:35:52 CET schrieb Dirk Eddelbuettel: | > On 25 February 2018 at 11:51, meik michalke wrote: | > | 'Additional_repositories' is meant for R package repositories, it won't | > | work with source code git repos.

Re: [R-pkg-devel] [FORGED] Re: How to (conditionally) use an archived package (without Suggests)?

> As already suggested: > - create a drat repository, > - place a copy of loon (from its repo source or the Archive section) in it > - add the repo to Additional_repositories > - using Suggests: is now permissible as the package is now useable > - the ':::' not declared warning should now go

Re: [R-pkg-devel] How to (conditionally) use an archived package (without Suggests)?

Am Sonntag, 25. Februar 2018, 06:35:52 CET schrieb Dirk Eddelbuettel: > On 25 February 2018 at 11:51, meik michalke wrote: > | 'Additional_repositories' is meant for R package repositories, it won't > | work with source code git repos. if a package is in 'Suggests' and can't > | be found > You

Re: [R-pkg-devel] How to (conditionally) use an archived package (without Suggests)?

On 25 February 2018 at 11:51, meik michalke wrote: | 'Additional_repositories' is meant for R package repositories, it won't work | with source code git repos. if a package is in 'Suggests' and can't be found You missed the part where we create packages ("R CMD build") out of source repos, and

[R-pkg-devel] stages of package loading

hi, i'm currently trying to figure out whether it is possible to tell a dependency that it was loaded as a dependency and by which package. the use case is this: - packages A and B both depend on package X - package X can be loaded independently, but checks if A or B are available - when

Re: [R-pkg-devel] [FORGED] Re: How to (conditionally) use an archived package (without Suggests)?

On Sun, Feb 25, 2018 at 11:16 AM, Rolf Turner wrote: > > Marius: > > Can you not, instead of > >> if(pkg == "loon" && !requireNamespace("loon", quietly = TRUE)) >> stop("Package 'loon' is not available.") > > do something like: > > if(pkg == "loon" &&

Re: [R-pkg-devel] [FORGED] Re: How to (conditionally) use an archived package (without Suggests)?

Marius: Can you not, instead of if(pkg == "loon" && !requireNamespace("loon", quietly = TRUE)) stop("Package 'loon' is not available.") do something like: if(pkg == "loon" && !requireNamespace("loon", quietly = TRUE)) { cat("Package 'loon' is not available.\n")

Re: [R-pkg-devel] How to (conditionally) use an archived package (without Suggests)?

Others may comment more knowledgeably, but I think what you want is impossible due to the combination of requirements. If you want to put it under additional repositories, I suggest Dirk Eddelbuettel's drat package as a simple way of generating the required repository structure. On Sun, Feb

Re: [R-pkg-devel] How to (conditionally) use an archived package (without Suggests)?

>> It does -- except for the 'warning': >> >> '::' or ':::' import not declared from: ‘bar’ >> 'loadNamespace' or 'requireNamespace' call not declared from: ‘bar’ > > That's because 'bar' is not in Suggests. Thinking a bit about it, the reference to