-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plans on CRAN? #17
Comments
I'm not sure, mostly because the way this package works is to modify some of its own files once it's installed. This feels like a bit of a grey area with CRAN, although I haven't seen anything explicitly prohibiting packages from modifying their own files after installation. If there's a precedent elsewhere for this that you're aware of I'd be happy to consider sending this to CRAN. The other option is to use the repository at gadenbuie.r-universe.dev: options(repos = c(
gadenbuie = 'https://gadenbuie.r-universe.dev',
CRAN = 'https://cloud.r-project.org'))
install.packages('shrtcts') |
Here's another vote for putting this on CRAN. My work mirrors CRAN and access to other remote repositories is blocked. Putting it on CRAN would be very helpful. |
yeah, I'm slowly working on releasing some of my GitHub only packages to CRAN. This is on the list, but it'll be a little bit before I can get to it. |
@hliebert I remember the conversation (issue) was A good news is RStudio now supports querying the shortcuts in |
The RStudio feature landed in RStudio 2021.09.0 "Ghost Orchid"
|
Ah, that's unfortunate.
I'm not sure how that would help. I just wanted to map shortcuts for a couple of functions I wrote myself. Basically installing packages from anywhere other than CRAN is blocked at my work. So is downloading archives. |
The RStudio update means that, as long as you're using RStudio 2021.09.0 or later — i.e. RStudio released after September, 2021 — shrtcts will work just fine because it can write to a user-writable folder. Without the RStudio update, I have to modify files inside the package contents (which is more of a gray area than an explicitly disallowed CRAN policy), which might not work in controlled package environments anyway. |
Got it, thanks for clarifying. Thank you for your work! Whenever you get around to submitting to CRAN, your effort is greatly appreciated. |
Well this is interesting... |
Indeed. Maybe store shortcuts with the login usernames? |
This package is amazing! Any plans to be on CRAN?
The text was updated successfully, but these errors were encountered: