Diff for /wikisrc/mailing-lists/tech-repository.mdwn between versions 1.6 and 1.8

version 1.6, 2010/01/20 13:05:55 version 1.8, 2010/01/20 13:50:09
Line 28  please fill in Line 28  please fill in
   
 please fill in  please fill in
   
   ### Experiences with Bazaar
   
   #### Jonathan Perkin (sketch)
   
   We use bzr at work (MySQL), and while it has a number of problems, it does make dev work easy.
   
   The Good
   
   * easy to use
   * shared repositories keep local disk usage down
   * commercial backing (Canonical)
   * cross-platform (works on Windows)
   * numerous GUI available
   
   The Bad:
   
   * slow
   * requires python
   
   The Ugly:
   
   * can be really slow
   * changing repository formats is a hassle
   
   A basic example workflow
   
   <pre>
   # create a local shared repository. all objects are held in a .bzr sub-directory, with branches essentially a lightweight checkout
   $ bzr init-repo bzr
   $ cd bzr
   
   # fetch HEAD, will take a long time, depending on connectivity
   $ bzr branch bzr+ssh://bzr.netbsd.org/netbsd-trunk
   
   # fetch netbsd-5, as we already have the majority of the code in netbsd-trunk (and therefore .bzr), this takes a fraction of the time
   $ bzr branch bzr+ssh://bzr.netbsd.org//netbsd-5
   
   # ok, let's do some dev work
   $ bzr branch netbsd-trunk netbsd-trunk-sketch-fix-msk
   $ cd netbsd-trunk-sketch-fix-msk; hack hack hack
   
   # the usual cycle of hack/commit/merge
   $ bzr diff # show uncommitted diffs
   $ bzr commit # commit to local clone
   $ bzr merge ../netbsd-trunk # update clone to latest local trunk, OR
   $ bzr merge bzr+ssh://bzr.netbsd.org/netbsd-trunk # merge directly from upstream
   
   # publish our tree for others to review/hack on
   $ bzr push bzr+ssh://bzr.netbsd.org/netbsd-trunk-fix-msk
   
   # got reviewed/tested, let's push it
   $ bzr merge bzr+ssh://bzr.netbsd.org/netbsd-trunk
   $ bzr missing bzr+ssh://bzr.netbsd.org/netbsd-trunk # show changeset differences
   $ bzr push bzr+ssh://bzr.netbsd.org/netbsd-trunk
   </pre>
   
   I personally find this approach a lot more natural than git's way of managing branches itself inside a single working directory.
   
 ***  ***
   
 ## Conversion experiences  ## Conversion experiences
Line 100  Next try: hg convert on pkgsrc Line 158  Next try: hg convert on pkgsrc
 helps it to cope with the output of cvs rlog -N -r1.66 pkgsrc/databases/rrdtool/Makefile (that's the easy one)  helps it to cope with the output of cvs rlog -N -r1.66 pkgsrc/databases/rrdtool/Makefile (that's the easy one)
 but then it tries to parse the output of (eg) cvs rlog -N -r1.19 pkgsrc/graphics/dcraw/Makefile and it's not clear  but then it tries to parse the output of (eg) cvs rlog -N -r1.19 pkgsrc/graphics/dcraw/Makefile and it's not clear
 to me how it could hope to get that one right just from cvs rlog, and all alternatives are going to be rather tedious  to me how it could hope to get that one right just from cvs rlog, and all alternatives are going to be rather tedious
 and I'm still not planning to learn Python this week.  and I'm still not planning to learn Python this week. If you feel more energetic, feel free to hand over patches.

Removed from v.1.6  
changed lines
  Added in v.1.8


CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb