Re: Perl 5.8 - 5.10 On Current Production System

2010-03-05 Thread C. P. Ghost
On Thu, Mar 4, 2010 at 6:13 PM, Matthew Seaman
m.sea...@infracaninophile.co.uk 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-5.10.1

 ===  perl-5.10.1 conflicts with installed package(s):
       perl-5.8.9_3

       They install files into the same place.
       Please remove them first with pkg_delete(1).
 *** Error code 1


 I supposed I could do a forced manual removal of perl, but isn't that what 
 the '-f'
 arg in the portupgrade is supposed to do?

 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\.*

THANK YOU! This is *exactly* what was holding me up from upgrading
to Perl 5.10.

 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.)

        Cheers,

        Matthew

-cpghost.

-- 
Cordula's Web. http://www.cordula.ws/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Perl 5.8 - 5.10 On Current Production System

2010-03-05 Thread Lowell Gilbert
Matthew Seaman m.sea...@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/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Perl 5.8 - 5.10 On Current Production System

2010-03-05 Thread Matthew Seaman
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 05/03/2010 15:22:05, Lowell Gilbert wrote:
 Matthew Seaman m.sea...@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...
 

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.

Cheers,

Matthew

- -- 
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
  Kent, CT11 9PW
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkuRJG0ACgkQ8Mjk52CukIxqrwCgiP3cq3jDDcJzRYIycSGD3FpL
SIsAn1cWMmeFinU6C9UTWdlJWb0LcTxC
=+Ede
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Perl 5.8 - 5.10 On Current Production System

2010-03-04 Thread Tim Daneliuk
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? 
-- 

Tim Daneliuk tun...@tundraware.com
PGP Key: http://www.tundraware.com/PGP/

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Perl 5.8 - 5.10 On Current Production System

2010-03-04 Thread Glen Barber
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
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Perl 5.8 - 5.10 On Current Production System

2010-03-04 Thread Leslie Jensen



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@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Perl 5.8 - 5.10 On Current Production System

2010-03-04 Thread Robert Huff

Tim Daneliuk writes:

  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 ?


Robert Huff





___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Perl 5.8 - 5.10 On Current Production System

2010-03-04 Thread Tim Daneliuk
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 to all for pointing to this.

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-5.10.1

===  perl-5.10.1 conflicts with installed package(s): 
  perl-5.8.9_3

  They install files into the same place.
  Please remove them first with pkg_delete(1).
*** Error code 1


I supposed I could do a forced manual removal of perl, but isn't that what the 
'-f'
arg in the portupgrade is supposed to do?

 


-- 

Tim Daneliuk tun...@tundraware.com
PGP Key: http://www.tundraware.com/PGP/

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Perl 5.8 - 5.10 On Current Production System

2010-03-04 Thread Matthew Seaman
-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 from Perl 5.8 to 5.10 (or whatever is current)
 cleanly?

 /usr/ports/UPDATING ;-)
 
 
 Thanks to all for pointing to this.
 
 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-5.10.1
 
 ===  perl-5.10.1 conflicts with installed package(s): 
   perl-5.8.9_3
 
   They install files into the same place.
   Please remove them first with pkg_delete(1).
 *** Error code 1
 
 
 I supposed I could do a forced manual removal of perl, but isn't that what 
 the '-f'
 arg in the portupgrade is supposed to do?
 

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.)

Cheers,

Matthew

- -- 
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
  Kent, CT11 9PW
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkuP6kAACgkQ8Mjk52CukIzOFwCcDWkYxJrX+nPwWpzhrWGBuLTO
MIIAn1wVGgCJc4nFdDdxmyXnuzbJ3kni
=LfKt
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Perl 5.8 - 5.10 On Current Production System

2010-03-04 Thread Tim Daneliuk
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 Daneliuk tun...@tundraware.com
PGP Key: http://www.tundraware.com/PGP/

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Perl 5.8 - 5.10 On Current Production System

2010-03-04 Thread Jonathan McKeown
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=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.)

Has this absolutely ludicrous change not been reverted with extreme prejudice 
yet? And is there a PR where we can add interesting suggestions as to what 
miseries should be inflicted on the person responsible for it?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org