Version control (git, mercurial) for R packages

Peter Langfelder Thu Feb 9 00:01:31 CET 2012
I'm exploring using a version control system
+1! welcome to the new millenium :-)
to keep better track of changes to the [R] packages I maintain. I'm
leaning towards git
I like 'git' too, but one thing to consider (though keep in mind that
I'm new to R, so I Could Be Wrong): R-forge

https://r-forge.r-project.org/

seems to be the "canonical" place to put R packages, and it's svn.
That can be finessed, e.g.,

http://cameron.bracken.bz/git-with-r-forge

FWIW, Tom Roche <Tom_Roche at pobox.com>

Peter Langfelder Thu Feb 9 00:01:31 CET 2012
I'm exploring using a version control system
+1! welcome to the new millenium :-)

to keep better track of changes to the [R] packages I maintain. I'm
leaning towards git
I like 'git' too, but one thing to consider (though keep in mind that
I'm new to R, so I Could Be Wrong): R-forge

https://r-forge.r-project.org/

seems to be the "canonical" place to put R packages, and it's svn.
There seem to be three canons: r-forge, Rforge, and for the Followers  
of Wickham, github. Four, if you count OmegaHat.
That can be finessed, e.g.,

http://cameron.bracken.bz/git-with-r-forge

FWIW, Tom Roche <Tom_Roche at pobox.com>

David Winsemius, MD
West Hartford, CT
On Feb 8, 2012, at 6:33 PM, Tom Roche wrote:

Peter Langfelder Thu Feb 9 00:01:31 CET 2012
I'm exploring using a version control system

+1! welcome to the new millenium :-)

to keep better track of changes to the [R] packages I maintain. I'm
leaning towards git

I like 'git' too, but one thing to consider (though keep in mind that
I'm new to R, so I Could Be Wrong): R-forge

https://r-forge.r-project.org/

seems to be the "canonical" place to put R packages, and it's svn.

There seem to be three canons: r-forge, Rforge, and for the Followers of
Wickham, github. Four, if you count OmegaHat.
Also googlecode (e.g. sqldf).

b.

That can be finessed, e.g.,

http://cameron.bracken.bz/git-with-r-forge

FWIW, Tom Roche <Tom_Roche at pobox.com>

--

David Winsemius, MD
West Hartford, CT

______________________________________________
R-help at r-project.org mailing list
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.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Peter Langfelder Thu Feb 9 00:01:31 CET 2012
I'm exploring using a version control system
+1! welcome to the new millenium :-)

to keep better track of changes to the [R] packages I maintain.
I'm leaning towards git
I like 'git' too, but one thing to consider (though keep in mind
that I'm new to R, so I Could Be Wrong): R-forge

https://r-forge.r-project.org/

seems to be the "canonical" place to put R packages, and it's svn. 
That can be finessed, e.g.,

http://cameron.bracken.bz/git-with-r-forge
Nice link - but I can't follow it.

Actual Situation:
- - Package on r-forge

Want to have:
- - git (github?) repo as my main cvs and
- - branch (release_x.y.z) for new release for r-forge
- - push branch release_x.y.z to r-forge to do it's magic.

So there are two initial steps:
1) Initial import of r-forge repo to git(hub) (should be easy)
2) setup of local git repo for package (is easy)

and then github is used as VCS

When a release should be done, the following needs to be done:
- - branch on git (easy)
- - push new branch to r-forge (how?)

now how could this be done easily?

can I do this with

  git svn commit

?

Cheers,

Rainer
FWIW, Tom Roche <Tom_Roche at pobox.com>

______________________________________________ R-help at r-project.org
mailing list 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.
- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :       +33 - (0)9 53 10 27 44
Cell:       +33 - (0)6 85 62 59 98
Fax :       +33 - (0)9 58 10 27 44

Fax (D):    +49 - (0)3 21 21 25 22 44

email:      Rainer at krugs.de

Skype:      RMkrug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk8ziuQACgkQoYgNqgF2egr/0gCfaZLJ78RK2qOhdJAllixQYlgc
Fw0An0lJnq2bdaCz+OlRDU5QYOMzWuut
=C/DE
-----END PGP SIGNATURE-----
Once upon a time r-forge had the option to sync from an external svn
repository, e.g. hosted on googlecode. I haven't seen it available for
some time, sadly. I'm sure many users would appreciate if this feature
came back with the new interface. Not sure if it could work with git
as well, though.

b.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 09/02/12 00:33, Tom Roche wrote:
Peter Langfelder Thu Feb 9 00:01:31 CET 2012
I'm exploring using a version control system
+1! welcome to the new millenium :-)

to keep better track of changes to the [R] packages I maintain.
I'm leaning towards git
I like 'git' too, but one thing to consider (though keep in mind
that I'm new to R, so I Could Be Wrong): R-forge

https://r-forge.r-project.org/

seems to be the "canonical" place to put R packages, and it's svn.
That can be finessed, e.g.,

http://cameron.bracken.bz/git-with-r-forge
Nice link - but I can't follow it.

Actual Situation:
- - Package on r-forge

Want to have:
- - git (github?) repo as my main cvs and
- - branch (release_x.y.z) for new release for r-forge
- - push branch release_x.y.z to r-forge to do it's magic.

So there are two initial steps:
1) Initial import of r-forge repo to git(hub) (should be easy)
2) setup of local git repo for package (is easy)

and then github is used as VCS

When a release should be done, the following needs to be done:
- - branch on git (easy)
- - push new branch to r-forge (how?)

now how could this be done easily?

can I do this with

?git svn commit

?

Cheers,

Rainer

FWIW, Tom Roche <Tom_Roche at pobox.com>

______________________________________________ R-help at r-project.org
mailing list 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.

- --
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel : ? ? ? +33 - (0)9 53 10 27 44
Cell: ? ? ? +33 - (0)6 85 62 59 98
Fax : ? ? ? +33 - (0)9 58 10 27 44

Fax (D): ? ?+49 - (0)3 21 21 25 22 44

email: ? ? ?Rainer at krugs.de

Skype: ? ? ?RMkrug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk8ziuQACgkQoYgNqgF2egr/0gCfaZLJ78RK2qOhdJAllixQYlgc
Fw0An0lJnq2bdaCz+OlRDU5QYOMzWuut
=C/DE
-----END PGP SIGNATURE-----

______________________________________________
R-help at r-project.org mailing list
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.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Once upon a time r-forge had the option to sync from an external 
svn repository, e.g. hosted on googlecode. I haven't seen it 
available for some time, sadly. I'm sure many users would 
appreciate if this feature came back with the new interface. Not 
sure if it could work with git as well, though.
One option is obviously to use a local git repo and then use git svn -
but my ideal setup would be to have one "development repo" on
git(hub), and one package release repo on r-forge, and whenever I
decide "yes, that is a release", branch it on git and push this to
r-forge.
By doing this, r-forge only contains releases, and git(hub) the
development history.

But thinking about it, a different r-forge VCS backend (git) would
also be an option.

Why was that option scraped?

Rainer
b.

On 9 February 2012 21:59, Rainer M Krug <r.m.krug at gmail.com> wrote:
On 09/02/12 00:33, Tom Roche wrote:
Peter Langfelder Thu Feb 9 00:01:31 CET 2012
I'm exploring using a version control system
+1! welcome to the new millenium :-)

to keep better track of changes to the [R] packages I 
maintain. I'm leaning towards git
I like 'git' too, but one thing to consider (though keep in 
mind that I'm new to R, so I Could Be Wrong): R-forge

https://r-forge.r-project.org/

seems to be the "canonical" place to put R packages, and
it's svn. That can be finessed, e.g.,

http://cameron.bracken.bz/git-with-r-forge
Nice link - but I can't follow it.

Actual Situation: - Package on r-forge

Want to have: - git (github?) repo as my main cvs and - branch 
(release_x.y.z) for new release for r-forge - push branch 
release_x.y.z to r-forge to do it's magic.

So there are two initial steps: 1) Initial import of r-forge repo 
to git(hub) (should be easy) 2) setup of local git repo for
package (is easy)

and then github is used as VCS

When a release should be done, the following needs to be done: - 
branch on git (easy) - push new branch to r-forge (how?)

now how could this be done easily?

can I do this with

git svn commit

?

Cheers,

Rainer

FWIW, Tom Roche <Tom_Roche at pobox.com>

______________________________________________ 
R-help at r-project.org mailing list 
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.

______________________________________________ 
R-help at r-project.org mailing list 
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.
- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :       +33 - (0)9 53 10 27 44
Cell:       +33 - (0)6 85 62 59 98
Fax :       +33 - (0)9 58 10 27 44

Fax (D):    +49 - (0)3 21 21 25 22 44

email:      Rainer at krugs.de

Skype:      RMkrug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk8zktEACgkQoYgNqgF2egrvIACeMwR6uIyJoLXvZSb4gvo7Opzm
S7YAnimWJjfDgHUlpdn7rPRXMXmZltWf
=gqtc
-----END PGP SIGNATURE-----