cvs commit: ports CHANGES

Joe Marcus Clarke marcus at FreeBSD.org
Sun Feb 29 15:44:08 PST 2004


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
> > 
> >   FreeBSD ports repository
> > 
> >   Modified files:
> >     .                    CHANGES 
> >   Log:
> >   Add the latest round of bsd.*.mk changes.
> 
> This is good, but we need more in this file about:
> 
>     On 5-CURRENT after the 5.2-RELEASE split, the default Perl version
>     has been updated from 5.6.1 to 5.8.2.
> 
> What's the recipe for handling this?
> 
> '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

-- 
Joe Marcus Clarke
FreeBSD GNOME Team	::	gnome at FreeBSD.org
FreeNode / #freebsd-gnome
http://www.FreeBSD.org/gnome
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/cvs-all/attachments/20040229/e0cc4c05/attachment.bin


More information about the cvs-all mailing list