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. ----- Original Message ----- From: "Mark Griffiths" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, March 06, 2003 8:49 AM Subject: RE: [Draconet-users] Builds launched without changes to codebase... > I would have thought that since tagging/labeling does not modify source > files, no build is required. A tag/label is simply associating a name with > a specific version. It has no chance of breaking/fixing the build. Can you > describe a labeling scenario that would require kicking off a new build? ------------------------------------------------------- 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
