This is a question to better my understanding of the relationship between core R versions and packages that work with them. It's not a complaint or criticism. Installed here is R-3.5.1. There are two packages that allow integration of R and GRASS that are not yet available for 3.5.1: rpy2 and spgrass7. Appreciating that package maintainers have day jobs that take priority over volunteer package maintenance, I ask only for thoughts on when copies of those two packages _might_ be available for 3.5.1. Regards, Rich
> On Oct 11, 2018, at 11:40 AM, Rich Shepard <rshepard at appl-ecosys.com> wrote: > > This is a question to better my understanding of the relationship between > core R versions and packages that work with them. It's not a complaint or > criticism. > > Installed here is R-3.5.1. There are two packages that allow integration > of R and GRASS that are not yet available for 3.5.1: rpy2 and spgrass7. > > Appreciating that package maintainers have day jobs that take priority > over volunteer package maintenance, I ask only for thoughts on when copies > of those two packages _might_ be available for 3.5.1. > > Regards, > > RichRich, Your best bet is to directly contact the package maintainers, as they would be the definitive source for timeline information on package updates. They ultimately control that workflow for third party packages, whether on CRAN or otherwise, and can give you some idea of current status and plans. Regards, Marc Schwartz
On Thu, 11 Oct 2018, Marc Schwartz wrote:> Your best bet is to directly contact the package maintainers, as they > would be the definitive source for timeline information on package > updates.Marc, Thank you, I will contact them. Being unfamiliar with standard practice I asked first. Best regards, Rich
You can contact them as Marc suggested by opening an account at bit (bitbucket/Atlassian) or git (github) Most prefer strongly to have a primary at git before going to Atlassian other code checkers so you can discover the package team there esp if any future development is in the pipes. Don't worry about it you dont have to be a founder or developer to have an account there :) BR On Thu, Oct 11, 2018 at 9:11 PM Rich Shepard <rshepard at appl-ecosys.com> wrote:> This is a question to better my understanding of the relationship > between > core R versions and packages that work with them. It's not a complaint or > criticism. > > Installed here is R-3.5.1. There are two packages that allow integration > of R and GRASS that are not yet available for 3.5.1: rpy2 and spgrass7. > > Appreciating that package maintainers have day jobs that take priority > over volunteer package maintenance, I ask only for thoughts on when copies > of those two packages _might_ be available for 3.5.1. > > Regards, > > Rich > > ______________________________________________ > R-help at r-project.org mailing list -- To UNSUBSCRIBE and more, see > https://stat.ethz.ch/mailman/listinfo/r-help > PLEASE do read the posting guide > http://www.R-project.org/posting-guide.html > and provide commented, minimal, self-contained, reproducible code. >-- ______________________________ Amit Mittal Pursuing Ph.D. in Finance and Accounting Indian Institute of Management, Lucknow Visit my SSRN author page: http://ssrn.com/author=2665511 * Top 10% Downloaded Author on SSRN Mob: +91 7525023664 This message has been sent from a mobile device. I may contact you again. _________________ [[alternative HTML version deleted]]
?maintainer in R accesses the package description file to provide maintainer info. No need to fool around with git or other software development repositories. Bert Gunter "The trouble with having an open mind is that people keep coming along and sticking things into it." -- Opus (aka Berkeley Breathed in his "Bloom County" comic strip ) On Thu, Oct 11, 2018 at 9:44 AM Amit Mittal <prof.amit.mittal at gmail.com> wrote:> You can contact them as Marc suggested by opening an account at bit > (bitbucket/Atlassian) or git (github) Most prefer strongly to have a > primary at git before going to Atlassian other code checkers so you can > discover the package team there esp if any future development is in the > pipes. > > Don't worry about it you dont have to be a founder or developer to have an > account there :) > > BR > > On Thu, Oct 11, 2018 at 9:11 PM Rich Shepard <rshepard at appl-ecosys.com> > wrote: > > > This is a question to better my understanding of the relationship > > between > > core R versions and packages that work with them. It's not a complaint or > > criticism. > > > > Installed here is R-3.5.1. There are two packages that allow > integration > > of R and GRASS that are not yet available for 3.5.1: rpy2 and spgrass7. > > > > Appreciating that package maintainers have day jobs that take priority > > over volunteer package maintenance, I ask only for thoughts on when > copies > > of those two packages _might_ be available for 3.5.1. > > > > Regards, > > > > Rich > > > > ______________________________________________ > > R-help at r-project.org mailing list -- To UNSUBSCRIBE and more, see > > https://stat.ethz.ch/mailman/listinfo/r-help > > PLEASE do read the posting guide > > http://www.R-project.org/posting-guide.html > > and provide commented, minimal, self-contained, reproducible code. > > > -- > > ______________________________ > > Amit Mittal > Pursuing Ph.D. in Finance and Accounting > Indian Institute of Management, Lucknow > Visit my SSRN author page: > http://ssrn.com/author=2665511 > * Top 10% Downloaded Author on SSRN > Mob: +91 7525023664 > > This message has been sent from a mobile device. I may contact you again. > > _________________ > > [[alternative HTML version deleted]] > > ______________________________________________ > R-help at r-project.org mailing list -- To UNSUBSCRIBE and more, see > https://stat.ethz.ch/mailman/listinfo/r-help > PLEASE do read the posting guide > http://www.R-project.org/posting-guide.html > and provide commented, minimal, self-contained, reproducible code. >[[alternative HTML version deleted]]
On Thu, 11 Oct 2018, Amit Mittal wrote:> You can contact them as Marc suggested by opening an account at bit > (bitbucket/Atlassian) or git (github) Most prefer strongly to have a > primary at git before going to Atlassian other code checkers so you can > discover the package team there esp if any future development is in the > pipes.Thanks, Amit. Rich