Re: [R-pkg-devel] Advice on R-forge to Github migration

2021-02-02 Thread Duncan Murdoch
Thanks again to all who wrote on this thread: rgl now lives in git, with the main website now https://github.com/dmurdoch/rgl. Thanks especially to Joshua, who did most of the heavy lifting of actually importing the R-forge material. Duncan Murdoch __

Re: [R-pkg-devel] Advice on R-forge to Github migration

2021-01-31 Thread Duncan Murdoch
On 31/01/2021 3:20 p.m., Joshua Ulrich wrote: On Sun, Jan 31, 2021 at 2:17 PM Duncan Murdoch wrote: Thanks to everyone who commented. A few replies inline: On 31/01/2021 1:21 p.m., Joshua Ulrich wrote: > I've moved history and issues from R-Forge to GitHub for half a dozen > R package

Re: [R-pkg-devel] Advice on R-forge to Github migration

2021-01-31 Thread Joshua Ulrich
On Sun, Jan 31, 2021 at 2:17 PM Duncan Murdoch wrote: > > Thanks to everyone who commented. A few replies inline: > > On 31/01/2021 1:21 p.m., Joshua Ulrich wrote: > > I've moved history and issues from R-Forge to GitHub for half a dozen > > R packages. I might be able to do this rgl. At minim

Re: [R-pkg-devel] Advice on R-forge to Github migration

2021-01-31 Thread Duncan Murdoch
Thanks to everyone who commented. A few replies inline: On 31/01/2021 1:23 p.m., Ben Bolker wrote: I think it should be fine to have your package in a subdirectory: this works as expected. remotes::install_github("dmurdoch/rgl/pkg/rgl") The only disadvantages to this structure are (1)

Re: [R-pkg-devel] Advice on R-forge to Github migration

2021-01-31 Thread Jeff Newmiller
Technically, git does not record file history... it records commit history, and reconstructs file history as needed. The contents of a file identify it uniquely among all commits ever made regardless of which directory it was ever in. IMO this is the main reason why git is superior and I put up

Re: [R-pkg-devel] Advice on R-forge to Github migration

2021-01-31 Thread Ben Bolker
I think it should be fine to have your package in a subdirectory: this works as expected. remotes::install_github("dmurdoch/rgl/pkg/rgl") The only disadvantages to this structure are (1) it's a little bit surprising to users (who might try install_github("r-forge/rgl" and wonder why it di

Re: [R-pkg-devel] Advice on R-forge to Github migration

2021-01-31 Thread Ben Bolker
I think it should be fine to have your package in a subdirectory: this works as expected. remotes::install_github("dmurdoch/rgl/pkg/rgl") The only disadvantages to this structure are (1) it's a little bit surprising to users (who might try install_github("r-forge/rgl" and wonder why it di

Re: [R-pkg-devel] Advice on R-forge to Github migration

2021-01-31 Thread Joshua Ulrich
On Sun, Jan 31, 2021 at 12:10 PM Duncan Murdoch wrote: > > rgl has been on R-forge for a long time, but I am now planning on > migrating it to Github. I really dislike git, but Github offers enough > benefits, and nowadays I'm familiar enough with them, that I think I'd > be better off there. > >

[R-pkg-devel] Advice on R-forge to Github migration

2021-01-31 Thread Duncan Murdoch
rgl has been on R-forge for a long time, but I am now planning on migrating it to Github. I really dislike git, but Github offers enough benefits, and nowadays I'm familiar enough with them, that I think I'd be better off there. The easiest way to do this would be to do almost nothing: just