Danek Duvall wrote:
> On Thu, Feb 28, 2008 at 12:26:57PM -0600, Norm Jacobs wrote:
>
>
>> David.Comay at sun.com wrote:
>>
>>>>> SUNWmutt/protoype_com:
>>>>>
>>>>> o line 120ff: Is there a reason that message files are going in
>>>>> /usr/share, rather than /usr/lib?
>>>>>
>>>>>
>>>> mutt elects to put them there, and there appears to be precedent:
>>>> SUNWpostgr-libs and SUNWgnome-dtlogin-integration, among others, also
>>>> prefer /usr/share.
>>>>
>>>>
>>> I think Norm Jacobs can provide some guidance here because I never can
>>> remember the correct convention.
>>>
>>>
>> This is the location that was recommended and agreed upon when we reworked
>> some of the rules to move away from monolithic message, header, man, ...
>> packages in SFW. At that time we got G11N to agree to letting us split the
>> monolithic message file package along with guidance on what to deliver. It
>> is the documented location in the README for the SFW gate
>> (http://sfwnv/README.txt) under "Integration Rules", item 8
>>
>> 8. All message files must be delivered in your packages as binary
>> message files (.mo). Your open source software component should
>> be built such that these message files are installed under
>> /usr/share/locale.
>>
>
> Ah, okay. Thanks, Norm. I'm a bit confused, then, why all the core OS
> messages are in .mo files in /usr/lib/locale, but perhaps that's the bug
> now ...
>
/usr/share/locale was what was recommended at the time. Apparently,
many pieces of open source software set it to /usr/share/localeby
default, though I expect that you can use --localedir=/usr/lib/locale to
change that for most, if not all of them when you configure them.
looking through libc, it appears that gettext() and friends will default
to /usr/lib/locale unless the software sets it otherwise. Perhaps we
need to revisit this particular piece of the rules.
-Norm
