'Twas brillig, and Thierry Vignaud at 14/03/12 16:23 did gyre and gimble: > On 14 March 2012 16:31, Colin Guthrie <[email protected]> wrote: >> 'Twas brillig, and Thierry Vignaud at 14/03/12 15:23 did gyre and gimble: >>> If you fear a server crash, you can use git svn and you've a full compact >>> local backup >> >> As a side note, it would be good to use git more. I think during the >> mga3 timeframe I'll try and look at the git infrastructure with a view >> to moving the various soft/ stuff over to git. > > The things is, some translators are used to svn, so switching to git > may not be easy for them. > > For dev, it can helps things, keeping unfinished stuff into branches > rather than in patch files that can got lost/forgoten > >> Packages I won't even begin to think about (it's too much of a pain) > > On contrary, I think this one would be easier since mgarepo is > supposed to hide svn though some packagers know they can > use svn directly.
Yeah this is true. I guess that needs to be addressed properly. I wasn't involved with our transiflex roll out (nor do I know much about i18n generally. I should really learn some day. >> but it would be good to have more official and better exposed git >> repositories > > other advantages are : > > - less used space on the server (disk usage exploded on the > server when switching from CVS to SVN) ; > > - also quite a lot less files on the server too (so less jobs for > saving & fscking) since cvs used on file per checked file whereas > svn (as configured in mdv) is using one file per transaction in > big directories > > - full history is backuped locally at relatively little space cost > (providing git gc is run regularly at least when using git-svn) > for quite a lot project, disk usage is actually smaller than svn > that keep a copy of everything in .svn, thus doubling disk usage > whereas git compressed history can be smaller (not for the full > drakx history for the last 11+years though :-) ) > > - quite a lot operations are faster (even if SVN was already an > improvement over SVN regarding this) due to local requesting > instead of network requests (eg: log, blame, ...) Sold! (but then I was already sold anyway :)) >> where appropriate, automatic patch generation for some >> packages (for example I use one for the initscripts package and I need >> to be careful to add in patches from others to the "official" git >> repository for it). > > At least this one should eventually die, shouldn't it :-) ? For various values of "eventually" :p This is a valid point in the case of initscripts but several scripts will likely live on for a while - tho' maybe they'll be migrated to other, more specific-to-use-case packages (e.g. the networking scripts and the storage related scripts might eventually be split up... maybe not much need for that tho' - who knows). Certainly I would see our variations from the upstream fedora versions reducing over time. A lot of our changes seem to be quite pointless already - i.e. no real gain from any practical perspective. I guess this variation will reduce as time goes by) But yeah, even if this one dies, it would be good to allow mgarepo to automatically checkout/clone the source along with the pagkage for easy development and patch regeneration etc. One day it might be super easy, but no real rush I guess. Col -- Colin Guthrie colin(at)mageia.org http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/
