Mark Glines wrote: > I've since made a patch that reapplies r38804 with a whitelist for a > small group of useful-looking items,
For the curious, that patch is attached. It's probably safe to apply right now, or we can wait until after the release, or we can handle the requirements of pir builds through some other means. I don't feel too strongly either way; I just don't want to see chromatic's optimization work get dropped on the floor. Mark
commit cb26e793c822b5592f6fe17fa6a90bc2960cf749 Author: Mark Glines <[email protected]> Date: Sat May 16 17:05:39 2009 -0700 [config] Redo r38804, but whitelist some key items. diff --git a/config/gen/config_pm.pm b/config/gen/config_pm.pm index 66cde45..d79190d 100644 --- a/config/gen/config_pm.pm +++ b/config/gen/config_pm.pm @@ -97,9 +97,18 @@ END END + my %p5_keys = map { $_ => 1 } $conf->data->keys_p5(); + # A few of these keys are still useful. + my @p5_keys_whitelist = qw(archname ccflags longsize optimize); + foreach my $key (@p5_keys_whitelist) { + delete($p5_keys{$key}); + } + while (<$IN>) { if (/\...@pconfig\@/) { for my $k ( sort { lc $a cmp lc $b || $a cmp $b } $conf->data->keys ) { + next if exists $p5_keys{$k}; + my $v = $conf->data->get($k); if ( defined $v ) { my $type = ref $v;
_______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
