Hi all,
should “SystemRequirements” of an imported package be listed in the description
file of a package?
General scenario:
- Package X imports Package Y.
- Package Y lists “libzzz” as SystemRequirements.
Should Package X list the SystemRequirements “libzzz” as well? (question
occurred @ http
Dear Dominik,
IMHO you only need to list "first order" dependencies: things that your
package directly uses. Listing higher order dependencies would be redundant
as they are listed in the packages that have them as first order dependency.
Best regards,
ir. Thierry Onkelinx
Statisticus / Statisti
It is important for me to get my package into CRAN.
I haven't gotten any answer from the CRAN maintainers. I already tried to
submit a version of the package before some months and haven't gotten any reply
then.
The replies you gave me (thanks to all engaged in the discussion) were mixed.
I still
Hi Stefan,
first of all, thank you for taking the time and effort to link Julia and R.
That said, I would strongly encourage you to go for a reticulate-like approach.
There's a good reason for that. Once you start mixing languages, you really
want to have some indication what code is ran in wha
Hi!
Thanks for pointing to the package "namespace".
I experimented with it but I couldn't really figure out how it is supposed to
work:
The following code leads to strange errors that I don't understand:
> nse <- list2env(list(data="x", asdf = 2))
> namespace::registerNamespace(name = "NewNam
Hi Stefan,
you need the function makeNamespace() to create the environment as a namespace.
Look at the examples in the help files, I found them rather instructive. I also
hope someone else chimes in to shed some light on whether or not that approach
would be acceptable.
Joris Meys
Statistici
When I execute the example, I also get a strange behaviour:
library(namespace)
ns <- makeNamespace("myNamespace")
assign("test",7, env=ns)
ls(env=ns)
When I now want to invoke any help for a function, I get a warning message:
> ?loadNamespace
Warning message:
In find.package(if (is.null(
You're right, that's enough to not dig any further. I remembered it from the
earlier days of devtools, but they removed that dependency ages ago. I also
believe now the namespace package predates the later changes to the namespace
mechanism. Forget what I said, I should have spent a bit more tim
I submitted the Package AQLSchemes on Dec 9, 2019. I corrected the errors
noted in the manual inspection and resubmitted it on Jan 9. I got the
message that it passed the automatic checks and was awaiting manual
inspection. I have not heard anything since. Do I need to resubmitt the
package? Or ho
foghorn::cran_incoming() will let you inspect the package queue.
(most likely if the package has been sitting this long it's not ever
going to move farther through the queue and you should resubmit. An
e-mail to the CRAN maintainers after you check the status would probably
be appropriate
On 09/04/2020 3:28 p.m., John Lawson wrote:
I submitted the Package AQLSchemes on Dec 9, 2019. I corrected the errors
noted in the manual inspection and resubmitted it on Jan 9. I got the
message that it passed the automatic checks and was awaiting manual
inspection. I have not heard anything sin
AFAIK, no, though if the upstream package cannot (or won't) be implemented
without that system requirement and it really is a requirement for this package
then you might want to indicate "libzzz via Package X" just to be clear for
users. If it isn't a requirement for most of your functionality t
Ok, thanks.
On Thu, Apr 9, 2020 at 1:46 PM Duncan Murdoch
wrote:
> On 09/04/2020 3:28 p.m., John Lawson wrote:
> > I submitted the Package AQLSchemes on Dec 9, 2019. I corrected the errors
> > noted in the manual inspection and resubmitted it on Jan 9. I got the
> > message that it passed the au
13 matches
Mail list logo
