On 06/30/2004 07:18 PM, David Abrahams wrote: [snip]
the testing process as header files changed states. Furthermore, it's not really clear what it means to test against a particular tag for a given library, when that library may depend on other libraries. It would be similar to dependency checking for rpm or debian packages. For example,
pkgA~1.1~ depends on: pkgB~1.1~ pkgC~2.3~ and, for example, pkgB~1.1~ depends on fileX~1.1~ fileY~1.4~ where pkg<name> indicates a package and file<name> means an actual file, and ~<unsigned>.<unsigned>~ signifies the version of either package or file depending on what precedes it. Now, how you do that with tags, is another question, but it certainly can be done with the method I proposed earlier using release.log's. In that case, instead of pkgA, there would be: pkgA.release.log.~1.1~ where 1.1 is just the version number of the release.log file.