From: Max H. <ma...@qu...> - 2009-05-14 11:08:55
|
Am 13.05.2009 um 15:55 schrieb David H.: > Hello all. > > I spent some time on the weekend thinking about our options of > migrating to another Source Control model. I was looking specifically > at git and bzr, I am leaving SVN to those who have already expressed > interest in it. If I get understand you right, you mainly thought about transiting the *package trees* to a new SCM, right? I still would also be highly interested in switching our codebase to git/bzr/svn. Makes branches etc. so much nicer. Local trees using git/ bzr/mercurial also make it very convenient to locally develop new features, such as support for alternate SCMs in "fink update" ... *g* > > For git, as well as bzr pulling information from a source is not hard > to implement. Bot bzr and git have the ability to pull branches using > HTTP which should get us around and firewall restrictions that users > might have in place. Note that SVN also offers this advantage (note that I think directly switching to git/bzr would be better, but wanted to mention this for completeness saker). > > As a first step I would suggest something like this: > Create an initial import of only the info file repository on > http://www.gitorious.org/ for git and https://launchpad.net/ for bzr. > That will enable us to put the necessary update functionality into > fink and test it without enabling it for the common user. Why not put those at SF.net, which offers git and bzr (both for projects and individual devs) ? The advantage being that we don't have to create loggins for tons of other sites? [...] > > What I have not considered is how to execute the actual switch for > existing users. I would think that the info file tree has to be > deleted and an initial full pull of the git or bzr branch executed. Actually, don't we already have code in place for "switching" from a dists tree installed by an installer, to one created using rsync/cvs ? It should be possible to adapt that. Bye, Max |