Re: [R-pkg-devel] is this expected behavior

Yes. Demo/test files need to use the library function to attach the package like any other user. On September 13, 2023 5:24:52 PM PDT, "Richard M. Heiberger" wrote: >I have a demo file that uses a function defined in the package. >when I force the demo to be run with >R CMD check --test-dir=de

Re: [R-pkg-devel] [Tagged] Re: roxygen style documentation for data sets

None of us here are lawyers, but a simple google search should take you to discussions such as [1]. There is a long history of debates about the upsides and downsides of restricting how people can use your source code. My short take is that a GPL license prevents anyone from stuffing your code

Re: [R-pkg-devel] roxygen style documentation for data sets

I thought roxygen supported documenting NULL constants for data. I do think roxygen ought to be able to co-exist with Rd files... but the claim that documenting data requires Rd files smells fishy to me. On September 21, 2023 1:30:11 PM PDT, Michael L Friendly wrote: >I am an RStudio user, and

Re: [R-pkg-devel] R_orderVector1 - algo: radix, shell, or another?

Have you read the output of order entered at the R console? On September 24, 2023 1:38:41 AM PDT, Jan Gorecki wrote: >Dear pkg developers, > >Are there any ways to check which sorting algorithm is being used when >calling `order` function? Documentation at >https://stat.ethz.ch/R-manual/R-deve

Re: [R-pkg-devel] R_orderVector1 - algo: radix, shell, or another?

You asked how order works. From the R source you can follow which C functions are executed, and since you seem familiar with C you can answer your own question. On September 24, 2023 11:10:53 AM PDT, Jan Gorecki wrote: >Hi Jeff, > >Yes I did. My question is about R_orderVector1 which is part of

Re: [R-pkg-devel] Warning: a function declaration without a prototype is deprecated in all versions of C

This error arises because you are not declaring the function properly before you call it... likely because you have not included the appropriate header file or because you have typoed the function call. If you provide a link to your package someone may point you more precisely to your error, bu

Re: [R-pkg-devel] Problem persists, was Re: Problem compressing vignettes for CRAN

R could care less about what is in PATH... there is however a difference between Windows parsing PATH and how CMD lets you quote things interactively. The whole point of PATH is to let you or R provide simple program names like qpdf without knowing where they are... Windows takes over and looks

Re: [R-pkg-devel] Failing to write config file in linux

Installed packages may not be modified because they are permitted to be installed with read-only access. You have no option to proceed in this direction. Configuration files are normally stored in the user's working directory. Dotfiles are a common convention in *nix operating systems, but in W

Re: [R-pkg-devel] Fortune candidate Re: Issue with R Package on CRAN - OpenMP and clang17

ROFL! Seconded! The quote itself has a bit of greybeard smell to it, but the "ran out of stuff to delete at 100GB with 1000 out of 6000 targets compiled" had me in stitches. On October 31, 2023 10:16:10 AM PDT, Dirk Eddelbuettel wrote: > >On 31 October 2023 at 19:58, Ivan Krylov wrote: >| [...]

Re: [R-pkg-devel] Rmarkdown fails if (quote) r (space) is used

A code chunk does always begin with a triple backtick at the beginning of a line. The term for what you encountered is "inline code" used to embed computed results into the markdown text as though you had typed them directly. Check out https://www.r-bloggers.com/2017/12/how-to-show-r-inline-cod

Re: [R-pkg-devel] [External] circular suggested packages

Richard ... they are by different maintainers. They also are built with completely different underlying technologies... creating a bitmap is easy, deciphering one is difficult and may not be necessary in the same workflow and there may be different compiled code available optimized for different

Re: [R-pkg-devel] How to fix: non-standard things in the check directory: 'NUL' ?

Rhub is not CRAN. Please include a link to your source package if you want help. If there is actually a bug in Rhub then this NUL error may not reflect the response you will get from CRAN if and when you submit. On December 13, 2023 12:58:41 AM PST, Friedemann von Lampe wrote: >Hi, > >when try

Re: [R-pkg-devel] Wrong mailing list: Could the 100 byte path length limit be lifted?

This is a narrow view of the world. As has been mentioned here by Tomas, the issue at this point is that a very widely-used operating system does not allow the absolute path to be longer than 254 characters unless users make possibly-breaking changes to their OS configuration. If a user is curre

Re: [R-pkg-devel] Warnings from upstream C library in CRAN submission

Type conversions are always a bit risky... this one appears to be likely to corrupt data. If they actually intended to truncate values like this then they should have cast explicitly. Looks like you need to report this to the SUNDIALS maintainers. On February 3, 2024 7:38:35 AM PST, Satyaprakas

Re: [R-pkg-devel] Changing package maintainers

Are you aware of this [1]? J. Random Lurker may not be a reliable source, and actual CRAN repo maintainers are probably a bit busy... [1] https://cran.r-project.org/web/packages/policies.html#Submission On February 8, 2024 8:37:50 AM PST, Josiah Parry wrote: >I intend to change the maintainer o

Re: [R-pkg-devel] [External] RcmdrPlugin.HH_1.1-48.tar.gz

Remove leading periods from all file names in the tar.gz. Use .Rbuildignore to handle such files in your dev directory if you need them. Maybe also look at [1]. [1] https://stackoverflow.com/questions/40950799/r-cmd-check-error-how-to-get-rid-of-hidden-files-and-directory-in-devel-r-pack On M

Re: [R-pkg-devel] [EXTERN] Re: @doctype is deprecated. need help for r package documentation

What is a "right side window"? Are you mixing up what R does and what RStudio does? I think I agree with Ivan that this is a question about the environment in which you are loading the package rather than anything in the package itself. On March 7, 2024 11:21:06 AM PST, "Ruff, Sergej" wrote: >

Re: [R-pkg-devel] [External] Re: [External] Re: Assistance Needed to Resolve CRAN Submission Note

so... your suggestion is not for CRAN, but for R-Core, who makes changes to R On May 18, 2024 6:03:55 PM PDT, "Richard M. Heiberger" wrote: >exactly. when the --as-cran detects the need for that NOTE, it could prefix >the initial instance of that NOTE with information about >updating the ti

Re: [R-pkg-devel] different build tools

Duncan's point about options is key... the build options set by default in devtools etc are generally configured to minimize the time required to identify the next big issue to address. Options appropriate for preparing to submit to CRAN are slow and inconvenient for developing. I recommend tha

Re: [R-pkg-devel] No email with confirmation link on resubmission of package

Did you increment the version number? On June 5, 2024 1:19:27 AM PDT, Paul Kabaila wrote: >(1) Today, I submitted my R package to CRAN using >devtools::submit_cran() >which resulted in an email from >CRAN Package Submission Form >cransub...@xmbombadil.wu.ac.at

Re: [R-pkg-devel] NOTEs in packages using Rust

I am not connected to CRAN (by a long shot), but if I were I would not accept any of the arguments you are making here. I don't know what you are talking about with respect to excluding files in tarring... you should be using the package build processes as documented in Writing R Extensions. A

Re: [R-pkg-devel] Incomprehensible warning while checking

Google for "http 403 error"... likely win-builder has multiple packages with links to Posit, and the Posit web server is throttling automated hits. Theoretically this is just a warning and you can try submitting to CRAN, but CRAN may have even less luck accessing Posit than win-builder. Submitti

Re: [R-pkg-devel] Incomprehensible warning while checking

Have you reviewed WRE 5.3? I don't have personal experience with R 4.4 much less the dev version, but it seems that often they add checks in new versions of R for rules that have been published but ignored. On June 28, 2024 4:00:06 PM PDT, Iris Simmons wrote: >Thank you Jeff! I'm not worried ab

Re: [R-pkg-devel] Is R-Forge dead?

I cannot/will not to help you do this, but there are people out there who disagree with me who put considerable effort into doing this... the search term you would need in order to find them is "monorepo". But please reconsider... the whole point of putting code into separate packages is to iso

Re: [R-pkg-devel] unregistered S3 methods in a package

I have been reluctant to pipe up on this because I am no expert on the dark corners of the S3 dispatch mechanism, but I think unregistered S3 methods in packages are verboten. Perhaps [1] will shed some light? [1] https://blog.r-project.org/2019/08/19/s3-method-lookup/ On September 4, 2024 11:2

Re: [R-pkg-devel] Installation error when submitting package to CRAN

You should not use "library(anything)" in a package. You should rely on the Imports: field in the DESCRIPTION file along with importFrom() in your NAMESPACE file, or the Suggests: field in the DESCRIPTION file and if (requireNamespace("anypackage")) {anypackage::somefun} else {# avoid using an

Re: [R-pkg-devel] R-extension requirement about third-party random number generators (RNG)

You mention that you did not like putting the rstream in the user API but there is nothing forcing you to have the user call your cpp function directly... there are lots of packages that use R glue functions as the API. I have not dug into Dirk's code, but having the native R seed management is

Re: [R-pkg-devel] Failed: Future File Timestamp Check

Packages are supposed to work when mounted in a read-only filesystem... using writeLines seems like a very bad idea since you can't assume the package install is writeable when it is run, and running code from tmp is a security hole. If you absolutely cannot think of a way around running code f

Re: [R-pkg-devel] Failed: Future File Timestamp Check

That was clear to me, and changes nothing about my comments. On February 4, 2025 3:27:34 PM PST, Josiah Parry wrote: >The file was written using writeLines() but it is just a normal R script >with normal function definitions and is included in the R/ directory. The >source code is just programmat

Re: [R-pkg-devel] Retrieving versioned csv datasets for use in an R package

Seconded... have the support for obtaining the desired file be completely initiated by the user, and explicitly pass the filename into the functions that use the data. It is also easier to trace which file was used in a past analysis this way... auto config seems convenient, but it is hard to re

Re: [R-pkg-devel] How and where do I document sysdata.rda

Did you seriously look for instructions and not find [1]? And why do you think the answer should not involve Rd files? Documentation in R packages is what Rd files are for. If you don't want to mess with Rd files then you have no choice but to use something like the Roxygen package to mess with