Date: Thu, 19 May 2011 14:04:55 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: rotkap@gmx.de, freebsd-ports@freebsd.org Subject: Re: New perl, why not: perl-after-upgrade Message-ID: <4DD51577.6080006@infracaninophile.co.uk> In-Reply-To: <l11fa8-tne.ln1@news.hansenet.de> References: <l11fa8-tne.ln1@news.hansenet.de>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig137EA9F481449D611402F091
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On 19/05/2011 09:30, Heino Tiedemann wrote:
> Hi,
>=20
> Is there e reason why in ports/UPDATING is this mentioned:
>=20
> ,----[ 20110517 ]
> | 0) Fix pkgdb.db (for safety): pkgdb -Ff
> | 1) Reinstall new version of Perl (5.14): env DISABLE_CONFLICTS=3D1 po=
rtupgrade ...
> | 2) Reinstall everything that depends on Perl: ...
> `----
>=20
>=20
> and not this:
>=20
> ,----[ 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
--=20
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matthew@infracaninophile.co.uk Kent, CT11 9PW
--------------enig137EA9F481449D611402F091
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk3VFXwACgkQ8Mjk52CukIxy2wCfaHyvS/J7Wg0wD+cJCyyCy/xk
hFMAoI0TjA+IgABM7l9vc6mNoN2J7Z+d
=BvLX
-----END PGP SIGNATURE-----
--------------enig137EA9F481449D611402F091--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DD51577.6080006>