I have an RFC patch series to Git to add gettext localization support to it. So that eventually you'll be able to configure Git to e.g. shout error messages at you in German. Won't that be a nice variant of the current abuse? I think so.
Here's the latest version of the patch series I posted to the Git mailing list.
For the Perl side of things (Git is partially implemented in Perl) I'm using libintl-perl's Locale::Messages. It was very pleasant to work with it. I wonder why more Perl projects don't use it instead of Perl-y libraries like Locale::Maketext.
Maybe it's just the GNU gettext dependency they're trying to get rid of, although libintl-perl
includes a Pure-Perl version of the tools it provides .mo
, so probably not.
Actually the way most open source projects do localization is "not at all". I don't blame them, I certainly can't be bothered most of the time. But I wonder to what degree we're losing potential users & contributors because of this.
There was a recent-ish study of social networks on GitHub where it was evident that a lot of Japanese Perl users had formed a social-ghetto amongst themselves. I've seen a few trending Perl repositories that only have README
files in Japanese.
Maybe better localization tools - and most of all - a commitment to use them would help to bridge some of that.
Since 5.12 got released a lot of bugfixes have been flowing into blead
and one new feature. The prctl()
support for $0
that I previously blogged about just got commited by Steffen Mueller.
With this patch you can finally killall
programs you write in perl on Linux without killing all of your perl processes indiscriminately.
Jesse Vincent uploaded the perl-5.12.0-RC3 release to the CPAN. It's important that that this release is tested to flag any potential release blockers. If none are found it'll be released as 5.12 on April 9.
Here's how you can do that:
All tests should have been successful. To install it (without touching your existing perl!) do:
Now you have an installed perl-5.12.0-RC3
in ~/perl5-rc3/installed/bin/perl
. Now just configure CPAN to install modules without nagging:
And then maybe try installing your favorite CPAN modules, or bundles that suck down a lot of them (using sudo
here because my ~/.cpan
is owned by root):
Of course the most useful think you can do is test it on your own in-house code. All the code on the CPAN has probably been tested with 5.12 already.
If you encounter any issues first check if they're listed in the errata or mentioned in the perldelta for 5.12.
if you think you've found a new bug please report it with the perlbug tool installed with perl-5.12.0-RC3.
According to git log
I've submitted 33 patches to perl core, I just submitted another one which on Linux changes this:
Into this:
If this patch gets applied doing killall onion
on 5.14 will get you a dead process instead of onion: no process found
, the same goes for ps(1)
and top(1)
which read the legacy process name by default. Before this patch the behavior of $0 assignment on Linux hadn't changed since perl 4.000 came out.