Re: [bug-gnu-libiconv] [PATCH] Fix character encoding aliases for OS/2

[KO Myung-Hun]

Bruno Haible wrote:
> Hi KO Myung-Hun,
> 
>> Serenity Systems and Mensys BV are still distributing eComstation, which
>> is successor of OS/2, commercially. See http://www.ecomstation.com
>>
>> And refer to Wikipedia <http://en.wikipedia.org/wiki/EComStation>.
> 
> And if I go to their forum
>   <http://tech.groups.yahoo.com/group/eComStation/messages?o=1>
> I get the impression that's a community about the size of the Haiku
> community - less than 10 people actively working on it.
> 

Ooops... I don't know about the Haiku at all, but there are at least 10
more people actively working on that forum. ^^


> I have finite time, and it is more important for me to fix i18n problems on
> Mac OS X (which has millions of users) or support Windows 7 symbolic links
> in gnulib.
> 

I know. You're right. I would not say that you should do something on
OS/2 codes, but please review and merge if ok.

>> If it is OS/2 maintainer, I willing to do it.
> 
> My problem with you as OS/2 maintainer is that for you, OS/2 is something
> different than what it used to be. The OS you are talking about is a
> shipment from Serenity, not from IBM. 

Why is this important ? What is important is that OS/2 is being sold and
maintained as an OEM, eCS, by Serenity and Mensys.

> The libc you are talking about is
> from netlabs.org, not EMX. 

Likewise. kLIBC is a successor of EMX, it has a source level
compatibility with EMX. And EMX is not maintained any longer, but kLIBC,
as you see at netlabs.org, is actively maintained.

And all the almost programs haven been ported from EMX to kLIBC.

> I have no guarantee that what you submit would
> work on the real OS/2 with the real EMX, for those users who have this
> still around.
> 

Those users can use the older versions for EMX. I don't know what you
meant by the 'real' OS/2, but all the codes being able to be run on eCS,
can be run on the 'real' OS/2.

And the libs built for kLIBC are usually distributed with a different
name. Mostly 'k' is prefixed.

> And I had a libiconv for DJGPP "maintainer" who sent me updates from 2001
> to 2007. Now, his parts are unmaintained.
> 

I think, it is natural. A person can maintain something, and if the
situation change, he can give up it. Instead, any other one can take it
again. It is natural on open sources, isn't it ?

It's possible that you also encounter the situation that you cannot
maintain this project and the others any longer at some point.

>> Currently, kLIBC is a successor of EMX, and actively maintained. See
>> http://svn.netlabs.org/libc
>>
>> Is it ok to send the patches for kLIBC ?
> 
> You can try, but you have no guarantee that any of the gnulib maintainers
> finds it worth spending time on.
> 

Ok. Thanks for your advice.

BTW, my patch for libiconv was rejected ?

-- 
KO Myung-Hun

Using Mozilla SeaMonkey 2.7.2
Under OS/2 Warp 4 for Korean with FixPak #15
In VirtualBox v4.1.18 on Intel Core i7-3615QM 2.30GHz with 8GB RAM

Korean OS/2 User Community : http://www.ecomstation.co.kr