summaryrefslogtreecommitdiff
path: root/make
diff options
context:
space:
mode:
authorAttila Molnar <attilamolnar@hush.com>2013-07-04 09:12:41 -0700
committerAttila Molnar <attilamolnar@hush.com>2013-07-04 09:12:41 -0700
commitfd0fa86da89ab4cefa778307088ef2552a05a170 (patch)
treefce1ad1b9cc1c8735a9d39f582a841dbdb9d6ca6 /make
parentf6d68c82e7f46a107f4b7593d1b19876fe0a9660 (diff)
parent9b29bedbc3b43bdca35369879b0d1848e95b9aa5 (diff)
Merge pull request #574 from SaberUK/master+build-comment-cleanup
Clean up unneeded build system comments.
Diffstat (limited to 'make')
-rw-r--r--make/utilities.pm10
1 files changed, 0 insertions, 10 deletions
diff --git a/make/utilities.pm b/make/utilities.pm
index 9281246fb..245ddd916 100644
--- a/make/utilities.pm
+++ b/make/utilities.pm
@@ -305,16 +305,6 @@ sub translate_functions($$)
$module =~ /modules*\/(.+?)$/;
$module = $1;
- # This is only a cursory check, just designed to catch casual accidental use of backticks.
- # There are pleanty of ways around it, but its not supposed to be for security, just checking
- # that people are using the new configuration api as theyre supposed to and not just using
- # backticks instead of eval(), being as eval has accountability. People wanting to get around
- # the accountability will do so anyway.
- if (($line =~ /`/) && ($line !~ /eval\(.+?`.+?\)/))
- {
- die "Developers should no longer use backticks in configuration macros. Please use exec() and eval() macros instead. Offending line: $line (In module: $module)";
- }
-
if ($line =~ /ifuname\(\!"(\w+)"\)/)
{
my $uname = $1;