Perl 5.8 -> 5.10 On Current Production System

Matthew Seaman m.seaman at
Fri Mar 5 15:34:14 UTC 2010

Hash: SHA1

On 05/03/2010 15:22:05, Lowell Gilbert wrote:
> Matthew Seaman <m.seaman at> writes:
>> You got bitten by an ill-considered change introduced after the UPDATING
>> instructions were written.  To work around it, you need to set
>> DISABLE_CONFLICTS when rebuilding the port, eg like this:
>>    # portupgrade -m DISABLE_CONFLICTS=yes -o lang/perl5.10 -f perl-5.8\.*
>> Please feel free to complain volubly about this: it's hand-holding for
>> newbies which annoys and incoveniences the vastly larger number of
>> non-newbies (ie. anyone who has been using the ports for more than a few
>> weeks.)
> It has occurred to me that teaching portupgrade to handle this would be
> a Simple Matter of Programming.  Maybe even a strategy as simple as
> adding the variable to the make command lines automatically any time
> '-o' is specified.
> I wonder whether I could write that change without actually learning ruby...

Probably it's easy enough to do that, but only at the cost of completely
turning off the otherwise valuable conflicts checking mechanism.  You'ld
actually want to be informed of any conflicts /except/ the ones you
always get in this sort of operation between the port being replaced and
the port replacing it.  The fundamental problem is that conflicts
checking has been moved to way too early in the sequence -- it even
blocks you from downloading the tarballs for any port that conflicts
with what you have installed.



- -- 
Dr Matthew J Seaman MA, D.Phil.                   7 Priory Courtyard
                                                  Flat 3
PGP:     Ramsgate
                                                  Kent, CT11 9PW
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla -


More information about the freebsd-questions mailing list