Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upI want to depend on littler, please export something #40
Comments
|
What message? edd@don:~$ r -e 'q()'
edd@don:~$ r -e 'cat("Hi Gabor\n"); q()'
Hi Gabor
edd@don:~$ |
|
I want to use it from an R package. Then if one loads my package, one gets
because I need |
|
Dunno. Can you not |
|
I depend on your package, so I don't think I can specify |
|
Try Else, I suppose, I could be silent if |
|
I can't do
An option would be great! I think this is a bug in I suppose this is not the regular |
|
I am not sure that an option would work, actually. |
|
Btw it looks like to find the executable from R, I need sg like
(from Maybe it makes sense to provide this as an |
|
Maybe. I can look at what |
|
BTW there is no |
|
So this, I guess, it close: R> littler:::test("cat(system.file(package='littler', 'bin', 'r'))")
[1] "/usr/local/lib/R/site-library/littler/bin/r"
R> |
|
Well, I took the code from |
|
Yes, I later read up on |
|
Thanks! Btw. I just found out that if you need to import I still think that an |
|
Well...now it is in there. It just a one-liner, really, and a few lines of roxygen. |
I want to use littler from my package, but I don't want to
Dependon it, because of the lengthy startup message. I think the message is useful in general, but maybe not so much iflittleris just the background machinery of another package.Then the problem is that I cannot use
Imports, either, because then I need to import sg to avoid anR CMD checkwarning. But there is nothing to import.I quite like the fact that
littlerdoes not export anything. But I think it might be worth exporting a little something so that I canImportthe package cleanly. E.g. how about importing a single variable or functionrwhich just points to the binary oflittler? That's even (slightly) useful, I don't need to callsystem.file(), just uselittler::r.Alternative suggestions are also welcome.