So why are we developing KBUS, rather than using some other messaging system?
(I'm going to assume you've seen the previous blog items on KBUS, and/or read the KBUS documentation on its Google code page.)
This is the corporate blog for Kynesim Ltd - a technology development company in Cambridge, UK. We do fun stuff involving automotive, consumer electronics, IoT, and various local startups.
So why are we developing KBUS, rather than using some other messaging system?
(I'm going to assume you've seen the previous blog items on KBUS, and/or read the KBUS documentation on its Google code page.)
So over the last week or so I've been working on adding commands to muddle so that we can store and restore "version" information for a build tree.
The basic idea is to be able to save enough information to a file to allow reconstructing the main build structure, and the content of every checkout.
A build description doesn't necessarily suffice for this, firstly because you don't actually have to specify a revision id for a particular checkout (one can default to HEAD), and secondly because the user of a build might have updated checkouts since the build description was first used to extract it.
So, here is some documentation for the result (so far, at least).