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: a...@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 _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"