Re: /usr/lib/locale/<locale> and locale-archive should remove before generating locales?
On Mon, Apr 07, 2003 at 02:03:32AM +0900, GOTO Masanori wrote:
[...]
> > I tried to generate all locales with 2.3.2, hit es_EC, edit /etc/locale.gen
> > and remove everything up to es_EC as usual, re-run locale-gen. hit
> > es_EC.UTF-8, edit /etc/locale.gen and remove everything up to es_EC.UTF-8,
> > and re-run locale-gen.
> > But locales from the two first runs are deleted :(
>
> Yes, it's intentional.
>
> Currently it does not remain old entries before generating locales
> using debconf. We force not to use the old locale entries.
> Debian is designed for upgrading old environment to new environment
> without any re-installations, so sometimes user can use old entries
> which were generated in the past but currently they're not selected.
> It may lead confusion. This "restriction" may be strong, but it's
> intuitive. Generating locales are described only in /etc/locale.gen.
> If you don't use debconf, then it does not cause any removal.
>
> In addition, locale-gen does not remove /usr/lib/locale/* files.
> "rm -rf /usr/lib/locale/*" is in locales.postinst.
Oops you are right, I certainly ran 'dpkg-reconfigure locales' instead
of locale-gen, sorry for this confusion.
But I selected "Leave alone" and my /etc/locale.gen never contained the
"XXX GENERATED XXX" string, and files were removed.
The problem semms to be that locales/locales_to_be_generated does no
more contain "Leave alone" after locales.config is run.
Maybe some tests from locales.postinst should be cut'n'pasted into
locales.config?
Denis
Reply to: