Bug#172439: Bug#156386: patch to fix this bug 172439 - nope
At Sat, 21 Dec 2002 14:56:34 +0900,
Masato Taruishi wrote:
> At 20 Dec 2002 16:05:06 +0100,
> Nagy Peter.1 wrote:
>
> > Actually, your patch doesn't fix bug #172439. The problem is in the
> > postinst script. If /etc/locale.gen exists, bug XXX GENERATED XXX is not
> > present in it, postint won't touch /etc/locale.gen.
>
> Oh, sorry. I misunderstood that these reports are the same bugs.
Agh, Jeff remove the Closes: from changelog...
> > I think this whole locale.postinst magic is quite confusing and should
> > be removed.
>
> I don't think so. I guess it's better config simply
> overwrote /etc/locale.gen no-matter-what or prompt in config
> that XXGENERATEDXX is not found or something like that.
"Prompting in config" is good idea. locale.gen is in /etc/,
so overwriting /etc/locale.gen is not fine.
> BTW, generating locales on postinst is very slow.
> I guess we need a locales package with all the supported locales
> by glibc which generates locales in build time. The size of
> the package is not very large. Gnome or KDE are larger than it at
> least. However, the package is large from the server or PDA developer's
> point of view. So it's better there are two locales packages. The first
> package consists of all the supported locales and the second package
> use locale-gen on postinst and they conflict with eath other.
Historically, locales included all readymade locale data, but
it's too large, so the current style was adopted.
Especially CJK/UTF-8 locales are tooooo slow to generate data,
so readymade locales package is useful.
> How about the following structure?
>
> Package: locales (consists of all locales)
>
> Package: locales-dev (includes locale-gen, no config script)
> Conflicts: locales
>
> Package: locales-conf(?) (includes config script)
> Depends: locales-dev
> Conflicts: locales, localeconf
I wonder such fine-grained is useful or not...
Simply two package; locales and locales-all is enough.
-- gotom
Reply to: