Re: Bug#644138: Bug 644138: kcc and heimdal-client both install /usr/bin/kcc
Wait a moment ... what about removing kcc package. (See below)
On Sat, Mar 03, 2012 at 01:07:28PM -0800, Russ Allbery wrote:
> Jelmer Vernooij <email@example.com> writes:
> > I think it would be reasonable for Heimdal to rename kcc to kcc.heimdal
> > or something like that.
This is, as I understand, our standard procedure but ... what about
removing kcc package after seeing how it is now.
> > Heimdal upstream has been shipping kcc since 2010, but we haven't
> > included it in Debian before, so that probably causes the least upgrade
> > issues.
> I would contact Heimdal upstream and ask if they'd be willing to change
> the name of the binary, given that it's a relatively new program and is
> much more recent than the other package.
There are so many encoding convertes. This one seems to be outdated and
not so popular and not maintained. (It used to be popular as I remember
but that may be as old as in 1998 when nkf was in non-free ...)
I locally have 2 of them:
libc-bin: /usr/bin/iconv (The most basic one without huristics)
nkf: /usr/bin/nkf (The best huristic Japanese optimized one)
As I quickly checked for japanese optimized ones, I found 3:
nkf popcon = about 2000 last upload [2011-05-31] active
kcc popcon < 200 last upload [2004-11-29] no change from oldstable
ack popcon < 100 last upload [2008-07-24] no change from oldstable
nkf : UTF-8 supported (in Description)
kcc ack: UTF-8 not supported (in Description)
Both kcc and ack maintainers are not active these dya as I vaguely