sword modules in portage

I have finally gotten around to something I’ve been wanting to do for a while: cleanup the modules for Sword, the text-reading software applications. I thought that the easiest way to handle the modules from here on out would be to create individual packages for each one. They used to be bundled all in one package called sword-modules, which is still in the tree for now, but it was a bit cumbersome to manage.

The new packages are going in the app-dicts category, and you’ll see them trickle in as I get around to adding them one at a time. There are a lot of sword modules altogether, and I’ll probably add all the ones that are freely distributable.

The irony of all this is that I don’t even use any of the Sword apps myself. I don’t like reading books on the computer. But, I know they are popular with some people, so I’m glad to take care of them if I can.

Eventually, I’ll make a new virtual ebuild for sword-modules that will pull in all the ones available based on your LINGUAS variable. It’ll probably be a while before that happens though.

Also, if you’re looking to roll your own ebuilds, there’s a new eclass in the tree, called sword-module. It cuts down on maintenance for me. I’m open to adding other dictionaries in the tree if someone has any — there’s no reason to use just the “official” ones.

Leave a Reply