Hi, I will save an ebuild for german sword here. It is just a copy of sword-modules, but I set up a list of files that are free in german. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 34932 [details] sword-modules-de-20040707.ebuild - The ebuild for german sword modules. Like described above.
I am not very fluent in German- I think it would be a good idea to have a sword-modules-intl package, but I would need a description of each module. Which modules are you including in this package? A couple notes on the ebuild, though- since there are no special unpacking things needed, you can completely remove the src_unpack() function. Also, if there are no 'offensive' modules to worry about here, you can take out the lines: if use offensive; then cp ${S}/newmods/* ${D}/usr/share/sword/mods.d/ || die fi Another option could be an international USE flag on the main sword-modules ebuild. Let me know your thoughts on all of this!
Normally I just make my ebuilds on my own, and that just because I want to have my files listened in the packages system of installed packages. So this is just a ebuild I thought other people would use it. But just feel free to change the ebuild, or integrate it to the sword-modules, or generate a -intl ebuild. Do whatever you want with it (just tell me here what you are doing, so I can remove this ebuild from my /usr/local/portage ebuilds and have a official one. anyhow, thanks for your comment, to remove the unpack function. I'm not very good in writeing ebuilds. Martin
USE="intl" emerge sword-modules; but I'd like to wait for the main crosswire server to finish upgrading before I bump the ebuild. I'd also like to add a few other languages before I do a version bump. But for now, your changes are now in the ebuild :).