From owner-freebsd-pkg@freebsd.org Fri Apr 28 04:02:12 2017 Return-Path: Delivered-To: freebsd-pkg@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7A164D54DC5 for ; Fri, 28 Apr 2017 04:02:12 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 6641CBC for ; Fri, 28 Apr 2017 04:02:11 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id C31A53AE87; Thu, 27 Apr 2017 21:02:05 -0700 (PDT) From: "Ronald F. Guilmette" To: Anatoly cc: freebsd-pkg@freebsd.org Subject: Re: Help please... Upgrade to pkg no workie In-Reply-To: <20170427233520.25251605@asd2> Date: Thu, 27 Apr 2017 21:02:05 -0700 Message-ID: <18908.1493352125@segfault.tristatelogic.com> X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Apr 2017 04:02:12 -0000 In message <20170427233520.25251605@asd2>, Anatoly wrote: >If for some reasons you still don't want to reinstall whole system, you >may try to build new perl from source. Thanks. I found this thing called perlbrew, which allows generating a freah new perl binary quite easily and *without* messing up an existing set of perl binaries and associated libraries. So that *would have been* a solution to the problem that I had *seemed* to be facing. But (sigh) in the end it turned out that I didn't need to upgrade Perl after all. I just needed to upgrade my *understanding* of my Perl program... the one I had built which tried to process some internationalized domain names, but which kept on crashing for rather mysterious resons. I read something that suggested that my Perl might not have the latest and greatest understanding of international character sets, so I figured that that was the problem. But it tuned out that it was just barfing because I had failed to convert input from UTF-8 into Perl's internal representation (of international characters). So, all's well that ends well. But thanks for the suggestions guys. I appreciate it.