Gettext issues (was Re: cvs commit: ports CHANGES)

Eivind Eklund eivind at FreeBSD.org
Mon Mar 1 02:42:48 PST 2004


On Sun, Feb 29, 2004 at 06:43:56PM -0500, Joe Marcus Clarke wrote:
> 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.

Talking of gettext: I've been toying with the idea of having WITHOUT_NLS
settable in sysinstall, or defaulting NLS to off.  I believe most FreeBSD
users will want the english version, even if translations are available.

As a such, I think inflicting the level of pain the gettext changes give
on our users unless they find a fairly obscure knob is a Bad Idea.

Any thoughts?

Eivind.


More information about the cvs-all mailing list