-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/03/2010 15:22:05, Lowell Gilbert wrote:
> Matthew Seaman 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 rebuildin
Matthew Seaman 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
On Thu, Mar 4, 2010 at 6:13 PM, Matthew Seaman
wrote:
>> However, when I run:
>>
>> portupgrade -o lang/perl5.10 -f perl-5.8\.*
>>
>> I get this problem:
>>
>> ---> Upgrading 'perl-5.8.9_3' to 'perl-5.10.1' (lang/perl5.10)
>> ---> Building '/usr/ports/lang/perl5.10'
>> ===> Cleaning for perl-
On Thursday 04 March 2010 19:13:36 Matthew Seaman wrote:
> 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
On 3/4/2010 11:13 AM, Matthew Seaman wrote:
> portupgrade -m DISABLE_CONFLICTS=yes -o lang/perl5.10 -f perl-5.8\.*
>
Thanks for that. I'm not sure to whom I'd complain and/or if it would
make any difference ;)
--
Tim
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/03/2010 17:05:08, Tim Daneliuk wrote:
> On 3/4/2010 10:13 AM, Leslie Jensen wrote:
>>
>>
>> On 2010-03-04 17:06, Tim Daneliuk wrote:
>>> Is there a recommended procedure I can read somewhere on how to
>>> upgrade an
>>> entire production system f
On 3/4/2010 10:13 AM, Leslie Jensen wrote:
>
>
> On 2010-03-04 17:06, Tim Daneliuk wrote:
>> Is there a recommended procedure I can read somewhere on how to
>> upgrade an
>> entire production system from Perl 5.8 to 5.10 (or whatever is current)
>> cleanly?
>
> /usr/ports/UPDATING ;-)
Thanks t
On 2010-03-04 17:06, Tim Daneliuk wrote:
Is there a recommended procedure I can read somewhere on how to upgrade an
entire production system from Perl 5.8 to 5.10 (or whatever is current)
cleanly?
/usr/ports/UPDATING ;-)
___
freebsd-questions@freeb
Hi,
Tim Daneliuk wrote:
> Is there a recommended procedure I can read somewhere on how to upgrade an
> entire production system from Perl 5.8 to 5.10 (or whatever is current)
> cleanly?
Have a look at the 20100205 entry of ports/UPDATING.
Regards,
--
Glen Barber
On Sun, Aug 08, 2004 at 06:52:31AM -0400, dave wrote:
> Is anyone using perl 5.8 on 5.2.1? I do a fresh install, cvsup my ports
> and source, install a new world and kernel, get all that working fine, then
> do the perl 5.8 install. This goes fine. I then do:
> use.perl port
> reboot and a
On Wed, May 12, 2004 at 03:32:24PM -0400, Robert Fitzpatrick wrote:
> I remember installing a package that said it required Perl 5.6 in the
> past, but cannot remember which one. I am using this box mainly for
> Postfix 2.0.16 and amavisd-new with SpamAssassin 2.63 and ClamAV 0.65. I
> also have Op
On Thu, Feb 27, 2003 at 07:03:53AM +, Rus Foster wrote:
> I've installed perl 5.8 and I know to get the system to use it I have to
> run something like useport perl but I can't remeber the exact command.
> Could someone remind me please
# use.perl port
Cheers,
Matthew
-
did you try using the cmd 'use.perl port' as root first? also, you can get
alot of those perl modules from ports also.. the ones I know off hand:
/usr/ports/devel
/usr/ports/lang
/usr/ports/net
/usr/ports/www
I believe 'LWP' is in /usr/ports/www/p5-libwww
On Mon, 14 Oct 2002, Tomoki Taniguchi
13 matches
Mail list logo
