libiconv is useful to systems that do not use glibc. While uclibc does have a configuration option which would provide libiconv, it is hacky and would still need a "break out" package to help it properly compile and work on a uclibc only system. I can keyword ~arm ~mips ~ppc. I would need the arch teams (or permission) to keyword ~amd64 and ~x86. Is the bsd team okay with this? Since the package is DEPEND="!sys-libs/glibc" there should be no problems with conflicts. I need this soon because I need to clear a mistake I made in constructing the hardened/linux/uclibc profiles. I included a package.accept_keywords because I blindly copied over from /etc/packages. This file should be removed.
nothing to do for bsd@ here, please feel free to cc arches
Thanks. TARGET: ~amd64, ~arm, ~mips, ~ppc, ~x86 I will take care of ~arm, ~mips, ~ppc myself. I need permission from amd64 and x86 teams to go ahead and keyword. They probably do not have uclibc based systems to test. Let me add here that I've been using this package for a long time on all those arches.
Keyword ~arm ~mips ~ppc
keyword ~amd64 ~x86