As kde-i18n now supports LINGUAS and could be used for every language, I think it would be nice if it would be included into the main ebuild kde. Regards, Alexander Reproducible: Always Steps to Reproduce: 1. 2. 3.
I disagree on two reasons: one, a lot of people don't need/want to install it, and two, the availability of languages changes a lot from release to release.
I agree that there are many people who don't use kde-i18n, but otherwise the world isn't native english speaking and I think there are more people using kde-i18n than poeple not using kde-i18n. My solution would be to add us and en to LANGS in the ebuild but don't install something if those two languages where (lonely) in LINGUAS.
Or install nothing if LINGUAS is empty. You could use LINGUAS="all" for all languages.
Yeah, I think I'll plan to do that. This will also work much better once portage supports linguas natively in the use flags, which was just fixed yesterday and should be out in the next version of portage.
Any update on this? (especialy since KDE 3.3.0 is out)
I've thought about this more, and I don't see any good reason to add kde-i18n as a subpackage of the kde meta ebuild. It's easy enough to get just by emerging it manually.
