New perl, why not: perl-after-upgrade

[Matthew Seaman]

On 19/05/2011 09:30, Heino Tiedemann wrote:
> Hi,
> 
> Is there e reason why in ports/UPDATING is this mentioned:
> 
> ,----[ 20110517 ]
> | 0) Fix pkgdb.db (for safety): pkgdb -Ff
> | 1) Reinstall new version of Perl (5.14): env DISABLE_CONFLICTS=1 portupgrade ...
> | 2) Reinstall everything that depends on Perl: ...
> `----
> 
> 
> and not this:
> 
> ,----[ man perl-after-upgrade ]
> | The standard procedure after a perl port (lang/perl5.X) upgrade is to
> | basically reinstall all other packages that depend on perl.  This is
> | always a painful exercise.  The perl-after-upgrade utility makes this
> | process mostly unnecessary.
> `----

Because upgrading from perl-5.10 or perl-5.12 to perl-5.14 is a very
different proposition to upgrading from perl-5.10.0 to perl-5.10.1
(which is the sort of change where perl-after-upgrade is useful.)

Principally there's no guarantee of binary compatibility for loadable
modules across that large a version bump. As quite a big proportion of
perl modules do involve loadable shared object code, which will have to
be recompiled, it is simpler to just recompile everything



-- 
Dr Matthew J Seaman MA, D.Phil.                   7 Priory Courtyard
                                                  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey     Ramsgate
JID: matthew at infracaninophile.co.uk               Kent, CT11 9PW

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 267 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20110519/b16bea69/signature.pgp