[REPOST] problem upgrading perl
dougb at FreeBSD.org
Thu Jun 25 17:48:49 UTC 2009
Scott Bennett wrote:
> On Tue, 23 Jun 2009 10:30:11 -0700 Doug Barton <dougb at FreeBSD.org>
> There ought to be an automated way to deal with the package issue that
> causes the failure of the entire update run just because it wants a human
> to type "make deinstall && make reinstall".
Sorry I wasn't clear, the inherent problem I described is with perl,
not with the ports. Because perl stores its libraries in a file
hierarchy based on version number (arguably, a feature) when you do a
straight upgrade from one version of perl to another IME the only
really good way to do that is to make a list of perl-related stuff you
have installed, delete everything, and reinstall. For those that only
have a few libraries installed using portmaster/portupgrade -r will
probably work, and is certainly worth a try.
>> Have you tried using the -x option to exclude it? You can also use the
>> -i option, although for a lot of ports that can get annoying.
> I had not, thanks to my having misread something in the portmaster man
If you have any suggestions for improving the text I'm open to them.
> However, since reading your reply, I have tried (without -R)
> # nice +18 portmaster -x perl-threaded-5.10.0 -rv perl-threaded-5.10.0_3
If this is a literal copy of what you did I'm surprised it worked
since you've placed the -v option between the -r and its argument.
> which did rebuild perl
Yes, I just checked the code and portmaster does not check the -x
argument for the main port specified in the command line. I'll take a
look at that.
> (along with many other already rebuilt ports, of
> course). At this moment, I have
> # nice +18 portmaster -x perl-threaded-5.10.0_3 -R -rv perl-threaded-5.10.0_3
> running, and it is currently rebuilding perl yet again. So the -x option
> appears to be useless, at least in this context.
You might want to be a little more careful with your adjectives. My
feelings aren't hurt but when you're asking for help, especially for
something you're not paying anything for, words like "useless" tend
not to make you any friends.
> I began using FreeBSD at 5.2.1. Along the way, my other complaints have
> largely been fixed, but the ports subsystem remains to this day the weakest
> part of all of FreeBSD. I realize that the problem of coordinating the
> installation and maintenance of such a widely diverse body of ports and
> packages is a complex one,
Having spent a non-trivial amount of time in the bowels of the ports
system I would argue that "complex" is a dramatic understatement.
> but the problems the current tools, dependency
> lists, Makefiles, etc. present to the user are often insoluble by anyone but
> an expert in the internal workings of each of the pieces of the subsystem.
> The packages subsystem is in about as bad shape, and in spite of the
> degree to which the two are intertwined, they really do not play nicely
Once again, being more careful with your rhetoric would go a long way
here. This is a volunteer project, and no one would argue that there
is nothing left to improve. Feel free to roll up your sleeves and get
to work. :)
This .signature sanitized for your protection
More information about the freebsd-ports