> > Yes, but only if you are doing a checkout/get by tag/label. :) > > In the case of a change to a version release tag/label, and the associated > get on that label, can dramatically change the source used for the build. > But I assume that right now draco doesn't support builds based on > label/tags. > > It would be good to be able to build based on a label/tag and/or a branch; > but that is another feature. And in that case, a change to a label/tag is > important.
Good point. I agree that if the root of a branch is moved, then a kicking a build is justified. BTW, the CVS repository code supports branches already. We need to get feature 648817 [1] implemented. This will give Draco the responsibility of tagging/labeling even before the source is fetched. I'm going to try and get a clear day to spend on this soon. -MG [1] http://sourceforge.net/tracker/index.php?func=detail&aid=648817&group_id=668 80&atid=516088 ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com _______________________________________________ Draconet-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/draconet-users
