ROOT has moved to Subversion

@Fons Any update on this?

Having this would be very helpful.

If you need help setting this up please let us know. You could then clone the repository with all branches.

Another call here for the git mirror to be set up.

I’d rather not spend the time (and waste your bandwidth) pulling down from the subversion repository…

Hi,

it is on my TODO for the coming days. Was working on some other issues to be fixed first. It is coming! Stay tuned.

Cheers, Fons.

Hello again,

sorry for being a little pushy, but I was wondering what was holding you back to provide a git-mirror. The import to git can be done quite easily and updates could be automatically published from svn->git so you wouldn’t really need to immediately change your other infrastructure to provide this.

Let us know what you need and we will try to help.

hello all,

I tried to compile root svn folder under MS Windows with VC++ Studio 2010 Express.
It places all binary and library file under Debug or Release directories.
and i dont know how and where to copy those files to get a working root system.

is there any script or somehing lik that?

thanks
YILMAZ

note: there is no such problem compiling in Linux systems

Hi,

First, you should have open a new thread for a new question…
Then how did you build Root exactly? Using cmake?

Cheers, Bertrand.

hi,

i have a clear description in this post:
[url]How can i compile root source on windows with Visual C++

thanks in advance

Why not Git? :frowning:

Hi all,

Is there any update on the status of a centrally supported git ROOT repository? It would be extremely useful, especially for ROOT developers.

(I personally believe that ROOT should move toward using git as the default version control software for MANY reasons, but one step at a time).

Cheers,

  • George

Though “git” is easy to learn (you may refer to Pro GIT, an online book), it still needs time for developers to transfer their work copies and get familiar with this distributed development environment. I think, “git-svn” is good enough for though who prefer git. Because ROOT repository is quite big, you’d better use “-r:HEAD” with “git-svn”, e.g.

The “-r:HEAD” parameter may save your network bandwidth.

FWIW I have pushed an import of the ROOT subversion history to github at github.com/bbannier/ROOT. I update this from time to time, but it should also be a good starting point for anyone working with git-svn against ROOT svn.

I managed to automatically include most svn branches as git branches, I only failed to import banches stored in subversion under branches/dev (might be possible to do this correctly by hand). I didn’t work on teaching git about merges it failed to automatically recognize though.

Since ROOT seems to become cleaner/more strict, e.g. regarding what is put into the global namespace or with less fuzzy implementations, having e.g. patch branches in git allows to cleanly see when something breaks in our code with e.g. git-bisect.

And having all of that available locally just uses around 600MB in a bare clone.

I just want to mention how immensely bbannier’s git repository is. I can switch between arbitrarily distant ROOT branches in a matter of seconds without touching the network. This is very useful for testing and debugging across different versions of ROOT.