Added by Jesse Zhang, last edited by Jesse Zhang on May 12, 2010  (view change)

Labels:

Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.

If you also feel it a pain to manage recipes with cvc, this page may be of some interest to you.

By 'manage' I don't mean checkout/cook/commit. The shortcomings of cvc are rather in finding out information about:

  • who touched the recipe since it's committed (good candidate to blame for bugs
  • how the recipe is changed between revision and revision
  • when, how and by who a particular line/action/patch was added to the recipe

These are certainly possible with cvc. It's just too slow and painful.

I tried to ease the pain by the following tools.

http://github.com/zhangsen/cvc2git

See the README for details. It's very slow too (since it's just a wrapper around cvc), but usable. And after the first time checkout, you get a normal git repository and things become fast

http://github.com/zhangsen/hg-cvc

This one is not finished (yet).