As k3b-0.10 did not compile for me today, I tried to copy k3b-0.10.ebuild to k3b-0.10.1.ebuild and it worked great. As I can read on the k3b sourceforge-page, this seems to be a bugfix release and should not require changes in build process or dependencies. So someone should just do this copying in CVS.
Created attachment 19949 [details] k3b-0.10.1.ebuild - i18n support included, don't forget to set LINGUAS Caleb: Hope it's o.k. to shameless copy your i18n code. ;) Is there a reason, not to zip the koffice/i18n ebuilds to a single one, too? O.k. - compile time, but an extra ebuild for every single application to include other languages than american english is not very user friendly (and increases the number of ebuilds, which slows down syncing). When will this 'need to touch ebuild problem' be fixed? Is there a bug open to follow?
Created attachment 19953 [details] k3b-0.10.1.ebuild - small fix, now only the languages you're interested in will be installed
Created attachment 20001 [details, diff] k3b-0.10.1-include-limits.patch Hi guys. This patch is needed for gcc-2.95.3 (Old box at work :P).
Or should I say for Gentoo 1.2 (glibc-2.2.5/gcc-2.95.3 issue ..).
Err, Ok, at the other end of the bug report is not common for me =) Basically this fixes the build not finding PATH_MAX ...
Carlo, Have you seen my latest kde-i18n ebuild? It uses a different scheme of manipulating SRC_URI to achieve the same thing. The bonus is now that now touching of the ebuilds is required.
make that "no touching"
I've committed 0.10.1 using a slightly modified version of Carlo's ebuild. Will need some testing.
>Have you seen my latest kde-i18n ebuild? If I had seen it, I probably wouldn't force you to work on the ebuild. Thanks for pointing me to it. Just merged the ebuild, it works fine for me. What happens, if someone sets LINGUAS to "foo bar"? Maybe there should be a test for illegal values performed!? And what about scanning the sources if the languages set in LINGUAS are supported by the application? A spare tarball download could be saved and the user be informed.
That's a good idea...I'll see what I can do.
Going to close this one as fixed, will work on linguas stuff separately. Let me know if there are problem with this ebuild.
Caleb, I know I should prob have added another bug, but what about the fixor for gcc-2.95.3 ?
Oops, got it now.