Rafael Garcia-Suarez (rgarcias...@gmail.com)

I don't think that reason alone was sufficient to go through the
hassle of setting up uupacktool.pl. Wasn't there a packaging reason as
well? Or maybe it was just for people reconstructing a bleadperl (or a
repository holding bleadperl) purely from the APC patches?

Basically, what will break if we unpack the binary files ?

I think that the trick was to add a packed version of the
"contaminated" file in the source code of the APC tools.

Well, with the forthcoming git move, that kind of problem should
disappear. We should probably get rid of all .packed files and add a
.gitattributes files at the root to record which files are binary.
(Versioned metadata. Yay)

PS. My @mandriva email address is dead since two years...

I must admit that I see no compelling reason to add this warning. It's
not extremely consistent, and not extremely useful.

To me it's a bug. Actually that might be caused by charnames storing
an arrayref in %^H. But I don't reproduce it with 5.10 (the script
below works). Do you have some test code ?

use strict;
use warnings;
use 5.01;
use charnames 'greek';
say "\N{sigma} is Greek sigma";
eval { say "\N{sigma} is Greek sigma"; };
eval ' say "\N{sigma} is Greek sigma"; ';

Thanks, applied, and $VERSION bumped to 0.26.