Hi Marek, This is a great idea, and something that has been requested by Ryan in the past:
http://bugzilla.mkgnu.net/show_bug.cgi?id=545 *** THIS IS CERTAINLY A DIRECTION WE WANT TO MOVE TO *** On Tue, 2006-11-14 at 08:20 +0100, [EMAIL PROTECTED] wrote: > Of course the tool should check for all cases if there is a version in the > history of updated files that is not included in the base label + list of > bugs and warn about it. > If such a tool doesn’t exist I’m going to write it, but it would be great > if I only need to extend it… Such a tool doesn't exist, but a lot of the infrastructure for building such a tool exists in scmbug_vdd_generator. You could write a new tool that essentially issues an activity_vdd --from=base_label --to=trunk/branch and receives an xml file that contains the changes. You could then go through the xml data to cherry pick the bugs from trunk/branch that should be included in the new build; and warn about missing history as you pointed out. There is already a lot of generic logic in src/lib/product/Tools/SCM_Functions.pm.in for manipulating an SCM system (checking in/out) and an example of this module in use in src/lib/product/Tools/Glue_Installer.pm.in. I would be willing to help you put together this tool. I can put a skeleton together, add the command-line flags you might need and essentially issue a VDD, You could checkout the sources from the CVS repository and sent patches as you make progress; I'll merge them in. How does this sound ? _______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
