> What you *could* do is trigger the build from loginfo (post-commit) > and update a moving tag if the build is successful. That way > your trunk can contain garbage, but the last successfully built > commit will have an unambiguous marker on it. Your users can > choose the unstable tip, > cvs checkout foo > > or the last known good version, > cvs checkout -rLAST_GOOD foo
But why would you to that from the loginfo? Wouldn't it be easier to have that tag moved by a virtual user, the dedicated test build machine, which is building and testing in a loop, everytime the compilation is correct? Maarten _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
