Date: Wed, 24 Jun 2009 17:28:10 -0500 (CDT) From: Scott Bennett <bennett@cs.niu.edu> To: freebsd-ports@freebsd.org, sergey.dyatko@gmail.com Subject: Re: [REPOST] problem upgrading perl Message-ID: <200906242228.n5OMSACv011415@mp.cs.niu.edu>
next in thread | raw e-mail | index | archive | help
On Tue, 23 Jun 2009 08:31:36 +0300 "Sergey V. Dyatko"
<sergey.dyatko@gmail.com> wrote:
>В Mon, 22 Jun 2009 21:12:17 -0500 (CDT)
>Scott Bennett <bennett@cs.niu.edu> пишет:
>
>SB> On Thu, 18 Jun 2009 11:42:51 -0700 Doug Barton
>SB> <dougb@FreeBSD.org> wrote:
>SB> >Jim Trigg wrote:
>SB> >> Actually, he was suggesting changing from perl\* to perl-\* so
>SB> >> it would only match the perl port.
>SB> >
>SB> >FYI, the \* at the end is not needed, 'portmaster perl-' will work
>SB> >just fine.
>SB> >
>SB> >> Unfortunately, that won't work as there is at
>SB> >> least one other port that will match that -- net/p5-perl-ldap
>SB> >> (portname perl-ldap).
>SB> >
>SB> >It's generally a good idea to check your facts before posting to
>SB> >the list. Since the glob code goes by the directory names
>SB> >in /var/db/pkg, and since the prefix will be there in the
>SB> >directory name, this won't be an issue.
>SB> >
>SB> >In any case, I updated the instructions for this, and the other
>SB> >portmaster examples in /usr/ports/UPDATING a couple days ago so
>SB> >hopefully no one else will stumble over this.
>SB> >
>SB> Thank you for doing that. Unfortunately, it might have been
>SB> more appropriate to have simply replaced that note with another
>SB> that cautions anyone attempting the perl upgrade that the upgrade
>SB> has not been fully tested against all ports that may list the new
>SB> perl as a build dependency. It should also warn that portmaster is
>SB> *NOT* a good tool to use for this upgrade, even if the note shows
>SB> how to attempt it. Using the specific port name for perl when
>SB> restarting the upgrade process, I was able to resume for a short
>SB> time. However, portmaster has two design problems that apply
>SB> here. The first is that if portmaster encounters a port that fails
>SB> to build properly, it stops cold, rather than continuing to build
>SB> other ports that do build correctly, summarizing the build errors
>SB> at the end. This means that each time an error occurs, it requires
>SB> a manual restart (after the error has been corrected) that will run
>SB> only until the next error is encountered. The second design problem
>SB> is that the -R option, which is supposed to avoid rebuilding ports
>SB> that have already been successfully rebuilt, nevertheless rebuilds
>SB> the specified dependency port--in this case,
>SB> perl-threaded-5.10.0_3--*every single time* without checking to see
>SB> whether it was already successfully built. This is terribly
>SB> time-consuming and wasteful. One might argue that the command says
>SB> to rebuild the port specified, but there really needs to be some
>SB> way to tell it not to do so. Back to the problems with the
>SB> builds...a half dozen or more port rebuild failures were
>SB> correctable by simply entering the failed port's directory, doing a
>SB> "make deinstall && make reinstall", and then returning to restart
>SB> (again) portmaster, which then, of course, began by rebuilding perl
>SB> another time (sigh). Full testing of the perl upgrade should have
>SB> made this process unnecessary, it seems to me. Eventually, though,
>SB> I encountered a problem with a port called
>SB> misc/gnome-icon-theme-2.26.0_1. (I do not use and haven't
>SB> knowingly installed gnome, so I really don't know why this port was
>SB> installed in the first place. OTOH, I also have a strong suspicion
>SB> that it can't simply be eliminated either.) The rebuilding of this
>SB> port aborted thusly:
>SB>
>SB> ===> Installing for gnome-icon-theme-2.26.0_1
>SB> ===> Generating temporary packing list
>SB> ===> Checking if misc/gnome-icon-theme already installed
>SB> Making install in 8x8
>SB> gmake[1]: Entering directory
>SB> `/usr/ports/misc/gnome-icon-theme/work/gnome-icon-theme-2.26.0/8x8'
>SB> Making install in emblems gmake[2]: Entering directory
>SB> `/usr/ports/misc/gnome-icon-theme/work/gnome-icon-theme-2.26.0/8x8/emblems'
>SB> gmake[3]: Entering directory
>SB> `/usr/ports/misc/gnome-icon-theme/work/gnome-icon-theme-2.26.0/8x8/emblems'
>SB> gmake[3]: Nothing to be done for `install-exec-am'. test -z
>SB> "/usr/local/share/icons/gnome/8x8/emblems" || ../.././install-sh -c
>SB> -d "/usr/local/share/icons/gnome/8x8/emblems" install -o root -g
>SB> wheel -m 444 'emblem-default.png'
>SB> '/usr/local/share/icons/gnome/8x8/emblems/emblem-default.png'
>SB> install -o root -g wheel -m 444 'emblem-new.png'
>SB> '/usr/local/share/icons/gnome/8x8/emblems/emblem-new.png' install
>SB> -o root -g wheel -m 444 'emblem-readonly.png'
>SB> '/usr/local/share/icons/gnome/8x8/emblems/emblem-readonly.png'
>SB> install -o root -g wheel -m 444 'emblem-symbolic-link.png'
>SB> '/usr/local/share/icons/gnome/8x8/emblems/emblem-symbolic-link.png'
>SB> install -o root -g wheel -m 444 'emblem-unreadable.png'
>SB> '/usr/local/share/icons/gnome/8x8/emblems/emblem-unreadable.png' (cd /usr/local/share/icons/gnome/8x8
>SB> && /usr/local/libexec/icon-name-mapping -c emblems) Can't locate
>SB> XML/Simple.pm in @INC (@INC
>SB> contains: /usr/local/lib/perl5/5.10.0/BSDPAN /usr/local/lib/perl5/site_perl/5.10.0/mach /usr/local/lib/perl5/site_perl/5.10.0 /usr/
>local/lib/perl5/5.10.0/mach /usr/local/lib/perl5/5.10.0 .)
>
>that's answer on you question. just reinstall p5-XML-Simple
Thanks, Sergey. I didn't know that the message was supposed to direct
me to p5-XML-Simple. I've deleted it, and I *think* I'm now past that problem.
Scott Bennett, Comm. ASMELG, CFIAG
**********************************************************************
* Internet: bennett at cs.niu.edu *
*--------------------------------------------------------------------*
* "A well regulated and disciplined militia, is at all times a good *
* objection to the introduction of that bane of all free governments *
* -- a standing army." *
* -- Gov. John Hancock, New York Journal, 28 January 1790 *
**********************************************************************
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200906242228.n5OMSACv011415>