Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 29 Feb 2004 18:43:56 -0500
From:      Joe Marcus Clarke <marcus@FreeBSD.org>
To:        obrien@FreeBSD.org
Cc:        ports-committers@FreeBSD.org
Subject:   Re: cvs commit: ports CHANGES
Message-ID:  <1078098236.62463.50.camel@shumai.marcuscom.com>
In-Reply-To: <20040229233524.GA48293@dragon.nuxi.com>
References:  <200402040638.i146cVAi035977@repoman.freebsd.org> <20040229233524.GA48293@dragon.nuxi.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--=-2KA8ycs/K9xYj5EdBpEs
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Sun, 2004-02-29 at 18:35, David O'Brien wrote:
> On Tue, Feb 03, 2004 at 10:38:31PM -0800, Joe Marcus Clarke wrote:
> > marcus      2004/02/03 22:38:31 PST
> >=20
> >   FreeBSD ports repository
> >=20
> >   Modified files:
> >     .                    CHANGES=20
> >   Log:
> >   Add the latest round of bsd.*.mk changes.
>=20
> This is good, but we need more in this file about:
>=20
>     On 5-CURRENT after the 5.2-RELEASE split, the default Perl version
>     has been updated from 5.6.1 to 5.8.2.
>=20
> What's the recipe for handling this?
>=20
> 'pkg_add -r <something_that_depends_on_perl>' will hose a 5.2-CURRENT
> system that started out life as a 5.1-CURRENT system or older.  Because
> perl 5.8 will be installed, splatting on top of the already installed
> perl 5.6.  portupgrade doesn't know that perl 5.8 is a newer version of
> perl; so it won't upgrade an installed perl 5.6 to 5.8 and fix all the
> dependencies of already installed ports.

You're right, it won't.  What I had to do (though mainly for gettext and
libpthread and not so much Perl) was a portupgrade -rf perl-5\*.  All
Perl modules need to be rebuilt under the new version of Perl so that
they can be found correctly.

Portmgr is kicking around the idea of a /usr/ports/UPDATING file similar
to the src version that is geared toward users.  CHANGES was mainly for
developers to let them know what changes have occurred to the ports
infrastructure.  With the recent ruby changes, it's clear we need
something that tells the users what changes they need to perform to
maintain a consistent ports tree.

Joe

--=20
Joe Marcus Clarke
FreeBSD GNOME Team	::	gnome@FreeBSD.org
FreeNode / #freebsd-gnome
http://www.FreeBSD.org/gnome

--=-2KA8ycs/K9xYj5EdBpEs
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQBAQnk8b2iPiv4Uz4cRAkI9AKCjJkUowmqqtfuDzmRqBOkQJvPktwCgk7yy
mSp3jujdltTo3i7oCArEOWE=
=CebF
-----END PGP SIGNATURE-----

--=-2KA8ycs/K9xYj5EdBpEs--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1078098236.62463.50.camel>