From cca68c9a93cb3d3c552c27c525b2744ceb751b1d Mon Sep 17 00:00:00 2001
From: "jake%acutex.net" <jake%acutex.net>
Date: Wed, 14 Nov 2001 03:44:07 +0000
Subject: [PATCH] We don't really need to look for fragments that are pulled in
 by [% INCLUDE %] or [% PROCESS %].  While removing this code bit doesn't
 allow us to seperatly check that those fragments exist and compile, they'll
 be checked atomatically when the the template that wants them is run through
 the process() routine by the 004template.t test.  This issue was raised
 because bug 98707 introduced a [% BLOCK %] element and the syntax for using
 that is the same as for including a template fragment.

---
 webtools/bugzilla/t/Support/Templates.pm | 15 ---------------
 1 file changed, 15 deletions(-)

diff --git a/webtools/bugzilla/t/Support/Templates.pm b/webtools/bugzilla/t/Support/Templates.pm
index 6e5fb29042ad..c15611d4660a 100644
--- a/webtools/bugzilla/t/Support/Templates.pm
+++ b/webtools/bugzilla/t/Support/Templates.pm
@@ -43,19 +43,4 @@ foreach my $file (@files) {
     }
 }
 
-# Now let's look at the templates and find any other templates
-# that are INCLUDEd.
-foreach my $file(@testitems) {
-    open (FILE, $include_path . "/" . $file) || next;
-    my @lines = <FILE>;
-    close (FILE);
-    foreach my $line (@lines) {
-        if ($line =~ m/\[% (?:INCLUDE|PROCESS) (.+?) /) {
-            my $template = $1;
-            push (@testitems, $template) unless $t{$template};
-            $t{$template} = 1;
-        }
-    }
-}
-
 1;