There is a new version of libiconv available at http://www.gnu.org/software/libiconv/
Steps to Reproduce:
Would be nice to see a the new version of libiconv in portage.
due to the past issues with this package it is hard masked. And I'm not convinced there is a good reason for this to be in the tree at all.
So, if this would be good, why? And can it be guaranteed -not- to break things again?
Oh I wouldn't know if this would break things. The reason I stumbled onto this package was that libiconv 1.8+ seemed to be needed by idnkit so I looked it up and found a newer version than the 1.7 which was in portage.
You might be right though that it isn't needed and should be banned.
well, anything that overwrites glibc's header files is ... Bad.
Agreed. But then the idnkit package sould be removed or changed so it doesn't need libiconv, as the iconv.h is already installed by glibc?
according to the build in my local tree it doesn't depend on libiconv.
Then I do not know. It did install it for me. Perhaps it was some setting I had or used. I re-emerged glibc and I could install idnkit after that so it seem to be all fine now.
I am very curious here, because libiconv is in package.mask and has been so for years, and if somone removes it? *shrug*
well, glad its resolved.