Re: [R-pkg-devel] Suggests with non-CRAN packages

On 10/01/2024 10:53 a.m., Dirk Eddelbuettel wrote: On 10 January 2024 at 16:25, Uwe Ligges wrote: | | | On 10.01.2024 15:35, Josiah Parry wrote: | > Thanks, all. As it goes, the package submission failed. The package that | > is suggested is available at https://r.esri.com/bin/ | >

Re: [R-pkg-devel] Suggests with non-CRAN packages

On 10/01/2024 9:35 a.m., Josiah Parry wrote: Thanks, all. As it goes, the package submission failed. The package that is suggested is available at https://r.esri.com/bin/ and as such provided `https://r.esri.com ` as the url in `Additional_repositor

Re: [R-pkg-devel] Suggests with non-CRAN packages

On 10 January 2024 at 16:25, Uwe Ligges wrote: | | | On 10.01.2024 15:35, Josiah Parry wrote: | > Thanks, all. As it goes, the package submission failed. The package that | > is suggested is available at https://r.esri.com/bin/ | > and as such provided `https://r.esr

Re: [R-pkg-devel] Suggests with non-CRAN packages

On 10.01.2024 16:29, Josiah Parry wrote: Well, I wouldn't say "obviously." It's not quite clear what a "standard" CRAN-like repository looks like unless you have an intimate knowledge of CRAN's structure. A repository r that works with install.packages(..., repos=r) i.e. needs PACKAGES

Re: [R-pkg-devel] Suggests with non-CRAN packages

Well, I wouldn't say "obviously." It's not quite clear what a "standard" CRAN-like repository looks like unless you have an intimate knowledge of CRAN's structure. Regardless, thank you for the feedback! I'll adjust the description file. On Wed, Jan 10, 2024 at 10:26 AM Uwe Ligges wrote: > > >

Re: [R-pkg-devel] Suggests with non-CRAN packages

On 10.01.2024 15:35, Josiah Parry wrote: Thanks, all. As it goes, the package submission failed. The package that is suggested is available at https://r.esri.com/bin/ and as such provided `https://r.esri.com ` as the url in `Additional_repositorie

Re: [R-pkg-devel] Suggests with non-CRAN packages

Thanks, all. As it goes, the package submission failed. The package that is suggested is available at https://r.esri.com/bin/ and as such provided ` https://r.esri.com` as the url in `Additional_repositories`. The request was to remove the additional repositories and provide instructions for packa

Re: [R-pkg-devel] Suggests with non-CRAN packages

From the CRAN polcies: "Packages on which a CRAN package depends should be available from a mainstream repository: if any mentioned in ‘Suggests’ or ‘Enhances’ fields are not from such a repository, where to obtain them at a repository should be specified in an ‘Additional_repositories’ field

Re: [R-pkg-devel] Suggests with non-CRAN packages

Thanks, both. I'm not familiar with Additional_repositories. Must the package source be specified there? Or can it be specified via documentation a la Rd file? On Wed, Jan 3, 2024 at 12:14 PM Uwe Ligges wrote: > > > On 03.01.2024 17:58, Duncan Murdoch wrote: > > On 03/01/2024 11:33 a.m., Josiah

Re: [R-pkg-devel] Suggests with non-CRAN packages

On 03.01.2024 17:58, Duncan Murdoch wrote: On 03/01/2024 11:33 a.m., Josiah Parry wrote: I have a scenario where I have an exported function that requires the installation a package that *is not* available on CRAN. The body of the function is generally: fx <- function() {    rlang::check_inst

Re: [R-pkg-devel] Suggests with non-CRAN packages

On 03/01/2024 11:33 a.m., Josiah Parry wrote: I have a scenario where I have an exported function that requires the installation a package that *is not* available on CRAN. The body of the function is generally: fx <- function() { rlang::check_installed("noncranpkg") noncranpkg::gx() } As

Re: [R-pkg-devel] Suggests with non-CRAN packages

Lovely, thank you! On Wed, Jan 3, 2024 at 11:43 AM Uwe Ligges wrote: > > > On 03.01.2024 17:33, Josiah Parry wrote: > > I have a scenario where I have an exported function that requires the > > installation a package that *is not* available on CRAN. The body of the > > function is generally: > >

Re: [R-pkg-devel] Suggests with non-CRAN packages

On 03.01.2024 17:33, Josiah Parry wrote: I have a scenario where I have an exported function that requires the installation a package that *is not* available on CRAN. The body of the function is generally: fx <- function() { rlang::check_installed("noncranpkg") noncranpkg::gx() } As req

[R-pkg-devel] Suggests with non-CRAN packages

I have a scenario where I have an exported function that requires the installation a package that *is not* available on CRAN. The body of the function is generally: fx <- function() { rlang::check_installed("noncranpkg") noncranpkg::gx() } As required, this package is in the Suggests field. B