Annotation of wikisrc/mailing-lists/tech-repository.mdwn, revision 1.13

1.1       spz         1: ## Requirements
                      2: 
                      3: A list of requirements for a possible replacement for CVS as repo software for NetBSD and pkgsrc so we don't keep starting over listing these (and forgetting half) all of the time:
                      4: 
                      5: - the license would be nice to be BSDish, must be open source and free to use
                      6: - the software should be includeable in NetBSD base without too much excess baggage
                      7: - it should be possible to do development on old or small hardware
                      8: - it must support automated updating of source trees
                      9: - it must support branches
                     10: - there should be a conversion for the present history (that actually works)
                     11: - the resulting repository must not break easily
                     12: - the software should be reasonably mature and reliable
1.3       spz        13: - checkout of a pkgsrc tree must be feasible on a 32MB system
                     14: - checkout of a stable pkgsrc tree and then updating select package subdirs to the latest version of the main branch should be possible
                     15: - lasting removal of legally tainted code must be possible
1.1       spz        16: 
                     17: Please add/correct.
                     18: 
                     19: ***
                     20: 
1.2       spz        21: ## Experiences in using the software
                     22: 
1.9       asau       23: ### Experiences with Fossil
                     24: 
                     25: #### Aleksej Saushev (asau)
                     26: 
                     27: I started using it before conversion tool were available
                     28: (basically it isn't available yet, to my knowledge Joerg is working on it),
                     29: in addition I wanted to start as soon as possible
                     30: and to try operation with no conversion tool available.
                     31: Thus I've tried to simulate working with "vendor branches".
                     32: 
                     33: For now Fossil lacks some essential features and has other severe problems:
1.10      asau       34: 
1.9       asau       35: 1. No support for vendor branches.
1.11      wiki       36: * Redundant to "There's no support for importing vendor source"?
1.12      asau       37: * No, it is different. I would import manually, if only some support were there.
1.9       asau       38: 1. It is impossible to merge between trees growing from the very root.
                     39: The initial commit is too special, this prevents using these trees for vendor branches.
1.11      wiki       40: * Fixed in [4e3cd6ce4e].
1.12      asau       41: * 2010-11-08, not in pkgsrc.
1.9       asau       42: 1. There's no support for importing vendor source,
                     43: even "addremove" command isn't in trunk at the time of writing.
1.11      wiki       44: * It has been merged to trunk and is part of the pkgsrc version.
1.12      asau       45: * No, it isn't part of pkgsrc version at the moment, TIAS.
1.13    ! wiki       46: * Sorry, you are right. Merged to trunk in [ceab53718f].
1.9       asau       47: 1. Merge state sticks. You can't undo it.
1.11      wiki       48: * Not sure what you mean, but "revert" resets the merge state since [d13054ce84].
1.12      asau       49: * This is quite recent (late October) fix, I didn't check it.
1.9       asau       50: 1. You can't amend your source when you've just merged, you are forced to commit after merge.
1.11      wiki       51: * To clarify, the merge has to be committed first, no separate commits are possible from the checkout before that.
1.9       asau       52: 1. You can't tune diff command to ignore RCS keywords.
1.11      wiki       53: * Since RCS keywords are not really a native command, it is no surprise. An external diff program can be used for this purpose though.
1.9       asau       54: 1. You can't diff single file between two given versions.
1.11      wiki       55: * diff --from version1 --to version2 path/to/file
1.12      asau       56: * That didn't work, and I'm not sure it works now. It used to ignore path-to-file argument. (It used to bail out when both "--from" and "--to" were used.)
1.9       asau       57: 1. There's no way to change commit messages.
1.13    ! wiki       58: * easily done via ui: select a commit and under "Other Links" you can find "Edit" (given the necessary permissions).
1.12      asau       59: * How? It should be possible via command line nevertheless.
1.9       asau       60: 1. There's no documented way to select commit messages of current branch, or branch by given commit id.
                     61: Or there's a bug preventing it.
1.11      wiki       62: * fossil info <commitid>
1.12      asau       63: * This isn't about "info" command, it is about "timeline"
1.13    ! wiki       64: --> Please clarify what you mean.
1.12      asau       65: * BTW, this command doesn't support "-R" flag, perhaps you have to check the source out to use it.
1.13    ! wiki       66: 1. Commands are under-documented, usage messages don't list many available options.
1.9       asau       67: This applies to trunk at least, there's a branch that states documentation as its goal.
                     68: 1. There's no convenient way to look at commit contents: files affected, diff.
1.11      wiki       69: * fossil ui and use a web browser
1.12      asau       70: * We don't have web browser in base system, this information should be accessible with command line.
1.9       asau       71: 
                     72: Some of above problems are reported.
                     73: 
                     74: Note, all problems above are usability problems, I didn't explore e.g. scalability,
                     75: Joerg did and had problems, but this is another story.
                     76: 
1.2       spz        77: ### Experiences with git
                     78: 
                     79: please fill in
                     80: 
                     81: ### Experiences with Subversion
                     82: 
                     83: please fill in
                     84: 
1.8       wiki       85: ### Experiences with Bazaar
                     86: 
                     87: #### Jonathan Perkin (sketch)
                     88: 
                     89: We use bzr at work (MySQL), and while it has a number of problems, it does make dev work easy.
                     90: 
                     91: The Good
                     92: 
                     93: * easy to use
                     94: * shared repositories keep local disk usage down
                     95: * commercial backing (Canonical)
                     96: * cross-platform (works on Windows)
                     97: * numerous GUI available
                     98: 
                     99: The Bad:
                    100: 
                    101: * slow
                    102: * requires python
                    103: 
                    104: The Ugly:
                    105: 
                    106: * can be really slow
                    107: * changing repository formats is a hassle
                    108: 
                    109: A basic example workflow
                    110: 
                    111: <pre>
                    112: # create a local shared repository. all objects are held in a .bzr sub-directory, with branches essentially a lightweight checkout
                    113: $ bzr init-repo bzr
                    114: $ cd bzr
                    115: 
                    116: # fetch HEAD, will take a long time, depending on connectivity
                    117: $ bzr branch bzr+ssh://bzr.netbsd.org/netbsd-trunk
                    118: 
                    119: # 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
                    120: $ bzr branch bzr+ssh://bzr.netbsd.org//netbsd-5
                    121: 
                    122: # ok, let's do some dev work
                    123: $ bzr branch netbsd-trunk netbsd-trunk-sketch-fix-msk
                    124: $ cd netbsd-trunk-sketch-fix-msk; hack hack hack
                    125: 
                    126: # the usual cycle of hack/commit/merge
                    127: $ bzr diff # show uncommitted diffs
                    128: $ bzr commit # commit to local clone
                    129: $ bzr merge ../netbsd-trunk # update clone to latest local trunk, OR
                    130: $ bzr merge bzr+ssh://bzr.netbsd.org/netbsd-trunk # merge directly from upstream
                    131: 
                    132: # publish our tree for others to review/hack on
                    133: $ bzr push bzr+ssh://bzr.netbsd.org/netbsd-trunk-fix-msk
                    134: 
                    135: # got reviewed/tested, let's push it
                    136: $ bzr merge bzr+ssh://bzr.netbsd.org/netbsd-trunk
                    137: $ bzr missing bzr+ssh://bzr.netbsd.org/netbsd-trunk # show changeset differences
                    138: $ bzr push bzr+ssh://bzr.netbsd.org/netbsd-trunk
                    139: </pre>
                    140: 
                    141: I personally find this approach a lot more natural than git's way of managing branches itself inside a single working directory.
                    142: 
1.2       spz       143: ***
                    144: 
1.1       spz       145: ## Conversion experiences
                    146: 
1.6       wiki      147: ### git
                    148: 
1.5       wiki      149: Conversion of all modules to git succeeded using fromcvs togit. The resulting git repository of src contains several errors where files have a wrong version (eg in hunt/Makefile the contents of the file on the vendor branch appear as tip of the master branch, which is quite wrong).
                    150: There have been no reports of errors in the other modules; this may be due to a lack of testing.
1.6       wiki      151: 
                    152: ### hg
                    153: 
                    154: Conversion of src failed. Afair the rest worked when using Mercurial 1.3.*. Alas, fromcvs tohg is not compatible with Mercurial 1.4 which is in pkgsrc now and is the version to use with Python 2.6 (afair). Two identified problems:
                    155: <pre>
                    156:         self.ui = ui.ui(interactive = False)
                    157: </pre>
                    158: wants to be
                    159: <pre>
                    160:         self.ui = ui.ui()
                    161:         self.ui.setconfig('ui', 'interactive', 'off')
                    162: </pre>
                    163: in /usr/pkg/share/fromcvs/tohg.py line 10 (easily fixed, obviously)
                    164: and
                    165: <pre>
                    166:         n = self.hgrepo.commit(files = files,
                    167:                                text = text,
                    168:                                user = user,
                    169:                                date = "%s 0" % date,
                    170:                                p1 = p1,
                    171:                                p2 = p2,
                    172:                                extra = {'branch': branch})
                    173: </pre>
                    174: needs to be replaces with something that works with the 1.4 commit that looks like this:
                    175: <pre>
                    176:     def commit(self, text="", user=None, date=None, match=None, force=False,
                    177:                editor=False, extra={}):
                    178: </pre>
                    179: which is where I remembered that I wasn't planning to learn Python this week.
                    180: 
                    181: Next try: hg convert on pkgsrc
                    182: <pre>
                    183: --- /usr/pkg/lib/python2.6/site-packages/hgext/convert/cvsps.py 2009-12-02 01:30:45.000000000 +0000
                    184: +++ /tmp/cvsps.py       2010-01-20 12:52:11.000000000 +0000
                    185: @@ -271,14 +271,14 @@
                    186:                  tags[rev].append(match.group(1))
                    187:                  branchmap[match.group(1)] = match.group(2)
                    188:  
                    189: -            elif re_31.match(line):
                    190: +            elif re_31.match(line) and re_50.match(peek):
                    191:                  state = 5
                    192:              elif re_32.match(line):
                    193:                  state = 0
                    194:  
                    195:          elif state == 4:
                    196:              # expecting '------' separator before first revision
                    197: -            if re_31.match(line):
                    198: +            if re_31.match(line) and re_50.match(peek):
                    199:                  state = 5
                    200:              else:
                    201:                  assert not re_32.match(line), _('must have at least '
                    202: @@ -357,7 +357,7 @@
                    203:  
                    204:          elif state == 8:
                    205:              # store commit log message
                    206: -            if re_31.match(line):
                    207: +            if re_31.match(line) and re_50.match(peek):
                    208:                  state = 5
                    209:                  store = True
                    210:              elif re_32.match(line):
                    211: </pre>
                    212: helps it to cope with the output of cvs rlog -N -r1.66 pkgsrc/databases/rrdtool/Makefile (that's the easy one)
                    213: but then it tries to parse the output of (eg) cvs rlog -N -r1.19 pkgsrc/graphics/dcraw/Makefile and it's not clear
                    214: to me how it could hope to get that one right just from cvs rlog, and all alternatives are going to be rather tedious
1.7       wiki      215: and I'm still not planning to learn Python this week. If you feel more energetic, feel free to hand over patches.

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