Package: perl Version: 5.20.0-6 Severity: minor With static builds (-Uuseshrplib, where /usr/bin/perl is statically linked against libperl), perl -V lies about the configuration because we install Config.pm from the shared build (-Duseshrplib). This has been the case for a long time on i386, and since 5.20.2-5 we use a statically built /usr/bin/perl on all architectures.
The situation is somewhat better with the 5.22 packaging, where we install two Config.pm files: once in perl-base under /usr/lib/<triplet>/perl-base and once in libperl5.22 under /usr/lib/<triplet>perl/5.22. The former Config.pm has the configuration from the static build and the latter from the shared build. However, the current @INC in the 5.22 packages has the perl-base directory at the very end, so on non-minimal systems with libperl5.22 installed, perl -V still lies because the libperl5.22 Config.pm takes precedence. If libperl5.22 is not present, 'perl -V' will show the correct configuration. The right order of @INC would probably be to put /usr/lib/<triplet>/perl-base right before /usr/lib/<triplet>perl/5.22. There's no configuration knob for this so it needs patching perl.c. I'm not aware of other bad effects with the current ordering so this is not a priority. -- Niko Tyni [email protected]
