From owner-freebsd-stable@FreeBSD.ORG Thu Aug 1 15:31:38 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5E61715E; Thu, 1 Aug 2013 15:31:38 +0000 (UTC) (envelope-from bsd-lists@1command.com) Received: from udns.ultimateDNS.NET (ultimatedns.net [209.180.214.225]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1ADBA2A75; Thu, 1 Aug 2013 15:31:37 +0000 (UTC) Received: from udns.ultimateDNS.NET (localhost [127.0.0.1]) by udns.ultimateDNS.NET (8.14.5/8.14.5) with ESMTP id r71FVoCk013556; Thu, 1 Aug 2013 08:31:56 -0700 (PDT) (envelope-from bsd-lists@1command.com) Received: (from www@localhost) by udns.ultimateDNS.NET (8.14.5/8.14.5/Submit) id r71FVjP1013555; Thu, 1 Aug 2013 08:31:45 -0700 (PDT) (envelope-from bsd-lists@1command.com) Received: from udns.ultimatedns.net ([209.180.214.225]) (UDNSMS authenticated user chrish) by ultimatedns.net with HTTP; Thu, 1 Aug 2013 08:31:45 -0700 (PDT) Message-ID: <622977670ec4e80b844c5c6c978ae6f6.authenticated@ultimatedns.net> Date: Thu, 1 Aug 2013 08:31:45 -0700 (PDT) Subject: Please remove Perl from ports From: "Chris H" To: "freebsd-perl" , "freebsd-stable" User-Agent: UDNSMS/2.0.3 MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Aug 2013 15:31:38 -0000 Greetings, I currently manage several RELENG_8 servers. Recent changes in the manner in which base && ports must be managed have resulted in more than a fair amount of grief. the migration from cv(sup) --> subversion required re-working long standing, carefully crafted management procedures to be pitched to the trash, and re-invented. A recent change to the Perl installation structure presents an entire new set of headaches, rendering up(grading|dating) near, if not completely impossible. Case in point; an i386 8.3-STABLE box with it's last update just prior to the Perl structure change, began a new update this morning via portmaster(8). As it reached 163/300 upgrade targets, the process died with a missing dependency error -- p5-XML-Simple. Exploring /var/db/pkg revealed that it had already been installed/upgraded (p5-XML-Simple-2.20). Any attempt to re-install/forceably upgrade the module failed with "p5-XML-Simple-2.20 not installed". According to /usr/ports/UPDATING; 20130612: AFFECTS: users of lang/perl* and any port that depends on it AUTHOR: az@FreeBSD.org lang/perl5.12 has been upgraded from version 5.12.4 to 5.12.5 lang/perl5.14 has been upgraded from version 5.14.2 to 5.14.4 lang/perl5.16 has been upgraded from version 5.16.2 to 5.16.3 The directory structure where Perl is installed has also been modified: "major.minor" is now used instead of "major.minor.patchlevel". The "perl-after-upgrade" script has been removed. Please rebuild all Perl ports and all ports that depend on it: # portmaster -r perl or # portupgrade -rf perl or # pkg install -fR perl # portmaster -r perl ===>>> perl is not installed ===>>> Aborting update Hmm... # ls /usr/local/lib/perl5 5.14 5.14.2 site_perl Yep. Perl is installed. Any attempt to upgrade/update *any* Perl, or Perl related ports fail. I think it's probably fair to say, that the restructuring of the Perl installation is the cause -- no? How does reading, and following the instruction(s) provided in /usr/ports/UPDATING help, or resolve such matters? WHY was this change *required*? How does this help FreeBSD's base users? Couldn't th(is|ese) changes been given enough forethought to have provided tools/procedures that guarantee/ ensure that those affected, can make the transition smoothly? That those who's income is directly affected by FreeBSD, be relatively unencumbered by the changes? While I recognize that many might argue that updating more frequently would eliminate most -- if not all of these issues. I can only say, that that _shouldn't_ be the case. For many, schedules don't always permit this, and if given the right tools, this wouldn't be an issue at all. While I also recognize that those whom haven't experienced these issues, all of this might just sound like a "rant". I don't believe that all of the problems generated by the changes needed to have occurred. So, in the end; why did Perl have to be relocated? Is my only recourse at this point to # cd / # rm -rf . slib the DVD into the slot, and push the reset button? Thank you for all your time, and consideration in this matter. --chris