Re: /usr/lib/locale/<locale> and locale-archive should remove before generating locales?
On Fri, Mar 28, 2003 at 10:41:04PM +0900, GOTO Masanori wrote:
> At Fri, 28 Mar 2003 00:31:20 +0100,
> Denis Barbier wrote:
> > On Wed, Mar 26, 2003 at 01:52:59PM +0900, GOTO Masanori wrote:
> > [...]
> > > Currently, our locales package do not remove /usr/lib/locale/<locale>
> > > and /usr/lib/locale/locale-archive. Glibc locale system looks both
> > > <locale> dir and locale-archive files to search the current locale's
> > > database. These locale database can store the generated locales. So
> > > this means that we can have very old locale entries in these locale
> > > database. The current locale-archive file accumulates a lot of locale
> > > database which were generated in the past but the current locales'
> > > debconf interface does not have such old entries and they are not
> > > updated.
> > >
> > > So the solution is: remove all directories in /usr/lib/locale and
> > > /usr/lib/locale-archive whenever we reconfigure or install or upgrade
> > > locales package in each time.
> > >
> > > I think simply removal for old locale entries is the best and the
> > > easiest way. Any comments?
> > Yes, I see no reason to choose a harder way.
> Thanks, I've now added in locales.postinst:
> # Update requested locales. Remove all old locale dir and
> # locale-archive before generating new locale data.
> if test -z $LEAVE_FLAG; then
> rm -rf /usr/lib/locale/*
> Removing all files/dirs might be problem. However at least there is
> no package to touch /usr/lib/locale on my machine, so I guess it's
The only one in unstable is:
Someone should probably fix that.
MontaVista Software Debian GNU/Linux Developer