[PATCH] Make --enable-internationalization default

Gaetan Nadon memsize at videotron.ca
Tue Jan 24 14:40:11 PST 2012

On 12-01-24 05:06 PM, Matt Turner wrote:
> On Tue, Jan 24, 2012 at 4:45 PM, Thomas Dickey <dickey at his.com> wrote:
>> Actually the issue relative to xterm was reported over in GenToo this
>> week.
> Samuli and I are Gentoo developers
>> It seems that xorg changes have broken a more than 10-year old
>> packaging arrangement.
> Sorry for trying to maintain previously unmaintained software?
>> That's a bug in your code, and cannot be excused by citing a user request
>> to provide configurability.
> Not sure who or what you mean. It was certainly a bug in Gentoo -- I
> didn't provide a knob to configure this feature.
I am a bit confused, this is a new X.Org module. Anyway, the comments I
made were in relation to the bug report which had nothing to do with
changing the default value of the configure option.

It's become clear to me that there were two distinct issues in this bug
report judging by the two separate patches. This is always a source of

Ok, let's talk about changing the default value. I don't know how it was
before this module became an xorg module, can one of the Gentoo folks
give a bit of historical background? Are there additional dependencies
that are needed to use i18n? Like fonts, libraries, special OS or
compiler features. Would any non Linux platform trip on something?

These are some of the reasons why usually features are not enabled by
default. Those who don't need/use those features don't want to have a
build break and have to "disable" this or that which are all things they
may not understand.

What has changed now is that module is part of xorg and has more
visibility and perhaps more users, on more platforms than it had before.
Possibly without our knowledge.

More information about the xorg-devel mailing list