From: Larry Evans (cppljevans_at_[hidden])
Date: 2004-06-30 20:14:03
On 06/30/2004 07:18 PM, David Abrahams wrote:
> 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.
pkgA~1.1~ depends on:
and, for example,
pkgB~1.1~ depends on
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:
where 1.1 is just the version number of the release.log file.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk