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

[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 didn't work and (2) setting up Travis machinery takes a 
little more effort to get all processes to work in the proper 
subdirectories (see the glmmTMB package for examples).

  I'm not very good at Git, but always get a bit confused when I try to 
track changes in a file that has moved ...




On 1/31/21 1: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.
> 
> The easiest way to do this would be to do almost nothing:  just declare 
> the the dmurdoch/rgl fork of r-forge/rgl is now where all new changes 
> will be committed.
> 
> Can anyone else who has done this migration tell me if there there any 
> disadvantages to this that I don't know about?  What I know:
> 
>   - I'll lose the bug reports and forum discussions that were sent to 
> R-forge.
>   - I'll need to do a bit of work to change dmurdoch/rgl to a more 
> standard R package layout, but this should be quite easy:  basically 
> just moving the files in pkg/rgl to the top level.  I assume "git mv" 
> will keep their history if I do this.
> 
> Duncan Murdoch
> 
> ______________________________________________
> R-package-devel using r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel