On Tue, Jun 19, 2012 at 6:21 AM, Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote: > Since the smokers are likely to need to install this from the CPAN > anyway for older perls wouldn't it make more sense not to put this in > core, and instead just make sure we have the relevant Config::* > plumbing needed to write modules like this? Smokers generally want to install as little non-core stuff as possible so we do want this in core. Plus, I'd rather have *one* API than two. This really isn't any different than other dual-life modules than have various fallbacks for older perls. I haven't yet been shown that the new perl-space stuff can provide what Config::Perl::V does as nicely as it does. Ultimately, I defer to Tux on this. We originally asked "Tux, how can you tell XXX about a perl's configuration?" and he said "You can't, but I'll write a module to do it for you". Whatever he says is the right way to do it is fine with me. -- DavidThread Previous | Thread Next