Date: Fri, 05 Mar 2010 10:22:05 -0500 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Perl 5.8 -> 5.10 On Current Production System Message-ID: <44d3zix082.fsf@lowell-desk.lan> In-Reply-To: <4B8FEA40.9040203@infracaninophile.co.uk> (Matthew Seaman's message of "Thu, 04 Mar 2010 17:13:36 %2B0000") References: <4B8FDA6A.9090308@tundraware.com> <4B8FDC32.6090204@eskk.nu> <4B8FE844.6060804@tundraware.com> <4B8FEA40.9040203@infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Seaman <m.seaman@infracaninophile.co.uk> 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... -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44d3zix082.fsf>