From: Nicholas Clark Date: Tue, 13 Oct 2009 17:02:46 +0000 (+0100) Subject: Note that a test that regen.pl was run is TODO. X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=08063926ad82ca2ea65fb34336bffad9b58f1ed7;p=p5sagit%2Fp5-mst-13.2.git Note that a test that regen.pl was run is TODO. --- diff --git a/pod/perltodo.pod b/pod/perltodo.pod index 3dbc923..b48782c 100644 --- a/pod/perltodo.pod +++ b/pod/perltodo.pod @@ -36,6 +36,24 @@ instead there is an intentionally simpler library, F. However, quite a few tests in F have not been refactored to use it. Refactoring any of these tests, one at a time, is a useful thing TODO. +=head2 Test that regen.pl was run + +There are various generated files shipped with the perl distribution, for +things like header files generate from data. The generation scripts are +written in perl, and all can be run by F. However, because they're +written in perl, we can't run them before we've built perl. We can't run them +as part of the F, because changing files underneath F confuses +it completely, and we don't want to run them automatically anyway, as they +change files shipped by the distribution, something we seek not do to. + +If someone changes the data, but forgets to re-run F then the +generated files are out of sync. It would be good to have a test in +F that checks that the generated files are in sync, and fails +otherwise, to alert someone before they make a poor commit. I suspect that this +would require adapting the scripts run from F to have dry-run +options, and invoking them with these, or by refactoring them into a library +that does the generation, which can be called by the scripts, and by the test. + =head2 Automate perldelta generation The perldelta file accompanying each release summaries the major changes.