2012/3/20 Thomas Weber <twe...@debian.org>: > On Tue, Mar 20, 2012 at 12:41:43AM -0400, Jordi Gutiérrez Hermoso wrote: >> Please consider hg, as it is what Octave core uses, and if we're >> moving OF to a DVCS, it would be best to consolidate the two projects. > > What's the advantage? Where precisely is octave-forge better off > with a DVCS?
I don't know, why did you stop using svn for Debian packages? Same situation. > Stop the bike-shedding. I'm not complaining about the colour of the bikeshed, but whether it should be a bikeshed at all or not. Right now it's more of a stump. Or a large trunk. >> I am starting to formulate plans in my head for doing something >> like automatically rebuilding and testing OF packages against >> development versions of Octave so we can catch bugs earlier, and it >> would help if OF stopped using svn, e.g. by using hg subrepos. > > I keep on wondering what the used VCS has to do with that. If I want > a tarball of the current version, I run 'svn update' and have the > latest sources, just like with 'hg pull' or 'git pull'. Everything > else is totally independent of the VCS. But the tarball *shouldn't* exist independently of Octave. The problem right now for example is that Octave-Forge packages are developed independently of Octave. On several occasions developers have shied away from using newer Octave features because, e.g. Debian is packaging older Octave versions. Such is the situation with fstat and zscore in the statistics package. If there could be two concurrent versions, with, say, DVCS branches, we could keep stable and current versions of OF packages to match Octave. Also, if both are using the same DVCS, hg subrepos would be very helpful. They're fairly transparent. git submodules are a corresponding nightmare, and this isn't just me talking. > Do you want to use a separate repo for every package? Like 100 hg > repositories? Sure, why, do you want to drop the corresponding 100 git repos from Debian? There really isn't much of a difference between 100 hg subrepos or 100 svn subdirectories. > Have you considered what managing developer access to such > a number of repositories means? It's one server, no matter how many repos there are. It hasn't been a nightmare for Debian packages. > The problem with testing OF packages has one simple solution - > enable pkg.m to do it. I want a unified build method that builds Octave and then builds and tests all OF packages against the same Octave build that just happened. Having consistent tools across this would be helpful. - Jordi G. H. ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
