This is a little bit of cobble documentation.
Cobble is a primitive source code control system, targeted at tarball (or part* "shar" archives) ftp'd from around the net.

It has many of the same advantages of most source code control systems: merging code changes becomes much easier. Cobble is targeted at merging locally written changes into a single "line" (as opposed to a tree or graph) of baselines. Cobble's primary advantage over other source code control systems, most of which allow more flexible source structures, is that cobble uses (optionally compressed) tar archives or shar archives as baselines, so you needn't keep large, uncompressed source trees around for long periods of time.

BTW, note that cobble is really a very simple tool, mostly just a wrapper around patch(1). There really isn't much more to it, than what is described in this document - and yet the benefits can still be large. If nothing else, cobble encourages us to be very methodical.

Cobble uses these steps, to accomplish its job:

After you've successfully built your sources, it's time to install the software. You can do this with "do-inst". "do-inst" defaults to running "make install", but this can be overridden by providing an "inst" script next to the tarball.
Moving forward to the next release of your baseline (.tar.gz, .tar.bz2, &c), assuming that the previous release was fully built using cobble. This is where the primary benefits of cobble are realized:
I like to put this shell function in my ~/.bashrc :
Advanced cobble usage.


Back to Dan's tech tidbits

You can e-mail the author with questions or comments: