keeping github packages up to date

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

keeping github packages up to date

Federico Calboli-3
Hi all,

more and more people (sadly) are putting stuff on github, with either no CRAN upload or an package.  So I am stuck with using devtools and install_github.

I know how to keep stuff from CRAN updated — how do I do the same for github stuff?

Cheers

F


--
Federico Calboli
LBEG - Laboratory of Biodiversity and Evolutionary Genomics
Charles Deberiotstraat 32 box 2439
3000 Leuven
+32 16 32 87 67





______________________________________________
[hidden email] 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.
Reply | Threaded
Open this post in threaded view
|

Re: keeping github packages up to date

Jeff Newmiller
Reinstall the updated versions however you originally did. The "obstacles" imposed by CRAN that cause package developers to forgo sharing there came about to confirm documentation, cross-platform compatibility and dependencies. With no referee enforcing such care in the environments you are pulling from, you cannot expect automated dependency management to work. You are riding a mustang in the Wild West... so have fun while it lasts... eventually bit-rot will break your library unless you freeze it (use packrat and keep old versions of R?).

On October 12, 2018 8:00:11 AM PDT, Federico Calboli <[hidden email]> wrote:

>Hi all,
>
>more and more people (sadly) are putting stuff on github, with either
>no CRAN upload or an package.  So I am stuck with using devtools and
>install_github.
>
>I know how to keep stuff from CRAN updated — how do I do the same for
>github stuff?
>
>Cheers
>
>F
>
>
>--
>Federico Calboli
>LBEG - Laboratory of Biodiversity and Evolutionary Genomics
>Charles Deberiotstraat 32 box 2439
>3000 Leuven
>+32 16 32 87 67
>
>
>
>
>
>______________________________________________
>[hidden email] 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.

--
Sent from my phone. Please excuse my brevity.

______________________________________________
[hidden email] 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.
Reply | Threaded
Open this post in threaded view
|

Re: keeping github packages up to date

prof.amit.mittal
I'd just check with a strip script checking for updates with devtools,
maybe every week and maybe when a mail pops from the git team, if
subscribed (pretty powerful about merges into the final software )

BR

On Fri 12 Oct, 2018, 21:03 Jeff Newmiller, <[hidden email]> wrote:

> Reinstall the updated versions however you originally did. The "obstacles"
> imposed by CRAN that cause package developers to forgo sharing there came
> about to confirm documentation, cross-platform compatibility and
> dependencies. With no referee enforcing such care in the environments you
> are pulling from, you cannot expect automated dependency management to
> work. You are riding a mustang in the Wild West... so have fun while it
> lasts... eventually bit-rot will break your library unless you freeze it
> (use packrat and keep old versions of R?).
>
> On October 12, 2018 8:00:11 AM PDT, Federico Calboli <
> [hidden email]> wrote:
> >Hi all,
> >
> >more and more people (sadly) are putting stuff on github, with either
> >no CRAN upload or an package.  So I am stuck with using devtools and
> >install_github.
> >
> >I know how to keep stuff from CRAN updated — how do I do the same for
> >github stuff?
> >
> >Cheers
> >
> >F
> >
> >
> >--
> >Federico Calboli
> >LBEG - Laboratory of Biodiversity and Evolutionary Genomics
> >Charles Deberiotstraat 32
> <https://maps.google.com/?q=Charles+Deberiotstraat+32&entry=gmail&source=g>
> box 2439
> >3000 Leuven
> >+32 16 32 87 67
> >
> >
> >
> >
> >
> >______________________________________________
> >[hidden email] 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.
>
> --
> Sent from my phone. Please excuse my brevity.
>
> ______________________________________________
> [hidden email] 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]]

______________________________________________
[hidden email] 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.
Reply | Threaded
Open this post in threaded view
|

Re: keeping github packages up to date

Federico Calboli-3
In reply to this post by Jeff Newmiller
On 12 Oct 2018, at 17:32, Jeff Newmiller <[hidden email]> wrote:
>
> Reinstall the updated versions however you originally did. The "obstacles" imposed by CRAN that cause package developers to forgo sharing there came about to confirm documentation, cross-platform compatibility and dependencies. With no referee enforcing such care in the environments you are pulling from, you cannot expect automated dependency management to work. You are riding a mustang in the Wild West... so have fun while it lasts... eventually bit-rot will break your library unless you freeze it (use packrat and keep old versions of R?).

I agree on all accounts — there is a thread here someplace where I expressed my displeasure at the fact people publish papers making a big deal of the fact they have github packages when it is obvious this is just a quick and dirty approach that creates as many issues (in terms of software management) that it might fix (in terms of whatever the code does).

Unfortunately some developers only release on github, or do not submit a new version to CRAN with all the bugfixes they put on github.  An unintended consequence of devtools.    

Cheers

F



>
> On October 12, 2018 8:00:11 AM PDT, Federico Calboli <[hidden email]> wrote:
>> Hi all,
>>
>> more and more people (sadly) are putting stuff on github, with either
>> no CRAN upload or an package.  So I am stuck with using devtools and
>> install_github.
>>
>> I know how to keep stuff from CRAN updated — how do I do the same for
>> github stuff?
>>
>> Cheers
>>
>> F
>>
>>
>> --
>> Federico Calboli
>> LBEG - Laboratory of Biodiversity and Evolutionary Genomics
>> Charles Deberiotstraat 32 box 2439
>> 3000 Leuven
>> +32 16 32 87 67
>>
>>
>>
>>
>>
>> ______________________________________________
>> [hidden email] 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.
>
> --
> Sent from my phone. Please excuse my brevity.

--
Federico Calboli
LBEG - Laboratory of Biodiversity and Evolutionary Genomics
Charles Deberiotstraat 32 box 2439
3000 Leuven
+32 16 32 87 67





______________________________________________
[hidden email] 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.