Date: Mon, 13 Oct 2014 21:08:05 +0200 From: Hans Petter Selasky <hps@selasky.org> To: Kurt Jaeger <lists@opsec.eu> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Problem with perl and SVK Message-ID: <543C2315.7040403@selasky.org> In-Reply-To: <543C200F.90905@selasky.org> References: <543C19AD.8070603@selasky.org> <20141013183706.GO29437@home.opsec.eu> <543C200F.90905@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/13/14 20:55, Hans Petter Selasky wrote: > On 10/13/14 20:37, Kurt Jaeger wrote: >> Hi! >> >>> When updating the system to the latest perl and SVK version in ports, I >>> am seeing this: >> [...] >> >> I'm seeing the same on 10.0p9 and perl 5.20. >> >>> Any ideas how to fix? >> >> This seems to bringt svk back in the game: >> >> cd /usr/local/lib/perl5/site_perl/5.20/SVK >> vi Util.pm >> >> replace >> >> use autouse 'List::Util' => qw( max(@) ); >> >> with >> >> use List::Util; >> >> but a short test shows: >> >> $ svk >> Use of uninitialized value $ARGV[0] in ucfirst at >> /usr/local/lib/perl5/site_perl/5.20/App/CLI/Command.pm line 116. >> SVK Documentation - Main index: >> [...] >> >> so the root cause is somewhere deeper. >> > > Hi, > > Using "use List::Util;" instead of autouse fixes the "svk diff" at least > over here. > > --HPS Hi, Seems to work: https://svnweb.freebsd.org/changeset/base/273059 The other perl warning has always been there. Will someone make a patch for the SVK port? --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?543C2315.7040403>