[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Coordination on standardizing gettext() in future POSIX
From: |
Alan Coopersmith |
Subject: |
Re: Coordination on standardizing gettext() in future POSIX |
Date: |
Wed, 22 Jan 2020 09:38:59 -0800 |
User-agent: |
Mozilla/5.0 (X11; SunOS i86pc; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 |
On 1/22/20 9:08 AM, Bruno Haible wrote:
Ulrich Drepper wrote:
Do you really like to require SunOS to loose backwads incompatiblity?
Overly dramatic. You just need one mode that is POSIX compatible. Many GNU
tools use POSIXLY_CORRECT_
The Solaris practice for keeping backward compatibility despite new evolutions
of the standards is to use /usr/xpg[457] directories. For example:
/usr/xpg4/bin/sh != /usr/bin/sh
/usr/xpg6/bin/ls != /usr/bin/ls
/usr/xpg7/bin/getconf != /usr/bin/getconf
There could be a /usr/xpg8/bin/gettext if POSIX gettext(1) ends up specifying
a different behaviour than the current Solaris implementation has.
This is absolutely correct, but only relevant if Solaris ever ends up fully
implementing XPG8, which is unlikely at this point. (Realistically, we'd
probably just make it a link to the /usr/gnu/bin/gettext we already ship
and widely use to build FOSS packages that expect the GNU behaviors.)
--
-Alan Coopersmith- address@hidden
Oracle Solaris Engineering - https://blogs.oracle.com/alanc
[The preceding is my personal opinion, and not an official statement of Oracle.]
- Re: Coordination on standardizing gettext() in future POSIX, (continued)
Re: Coordination on standardizing gettext() in future POSIX, Shware Systems, 2020/01/21
Re: Coordination on standardizing gettext() in future POSIX, Shware Systems, 2020/01/21
Re: Coordination on standardizing gettext() in future POSIX, Shware Systems, 2020/01/22
Re: Coordination on standardizing gettext() in future POSIX, Shware Systems, 2020/01/22