Hi Nilo, This sounds like a feature that could be useful. Although I am a little confused as to what exactly you are trying to do.
http://bugzilla.mkgnu.net/show_bug.cgi?id=1416 I thought you might want to only validate the installation worked, similar to: http://bugzilla.mkgnu.net/show_bug.cgi?id=358 On Tue, 2009-08-11 at 18:03 -0300, Nilo Garcia Silveira wrote: > But, on my context, I need a validation if the committed files were What is your context ? > included on the bug/issue on bugtracker. So, I'll implement a new > policie on the Glue script. > In my first analisis, I'll need change the following files: > C:\tools\scmbug-0.26.15\share\scmbug\lib\Scmbug\Glue\Glue.pm > C:\tools\scmbug-0.26.15\share\scmbug\lib\Scmbug\Daemon\Bugtracker.pm > C:\tools\scmbug-0.26.15\share\scmbug\lib\Scmbug\Daemon\Bugzilla.pm > C:\tools\scmbug-0.26.15\share\scmbug\lib\Scmbug\Daemon\Integration.pm When I first read this email, I thought you wanted to add a policy in the daemon to verify that what was attempted to be added in the issue-tracker was in fact added. Is this what you are trying to accomplish ? If so, why would you need to modify Glue.pm ? This sounds like it should be developed entirely on the Daemon. > If you thing this a nice feature, tell me how I can share it. > Do you have some tip to give me? How can you be sure that your validation is correct ? How will you do it ? How can you be sure that if a new version of the issue tracker becomes available that your validation policy will work against it ? Will you need another policy that validates the validation ?
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
