Created attachment 364052 [details] ooofbtools-2.25.ebuild Updated license (current is LGPL-2) and homepage. Because of file upload change of Google Code upstream had to switch source distributing to Google Disk (so, availability of sources requires authorization in Google Account; autofetch is unavailable, so SRC_URI in attached ebuild is empty, mirroring should be done prior to addind ebuild): https://drive.google.com/?tab=mo&authuser=0#folders/0B8S3GXOT5EY9ZGU4RU52ZHNSQTg For current version (up to < 2.18) major functionality of extension (text corrector) is broken (incompatible) with LibreOffice4. Currently uploaded ebuild is just a version bump of existing 2.12 version. It works well enougth, but needs in some fixes: 1. office-ext-r1 eclass seems to miss installation of docs (items of added DOCS massive are ignored), ChangeLog* files are skipped. I think, it will be correct to report it in separate bug. 2. Ebuild should provide handling of LINGUAS USE EXPAND (at least in selecting installed versions of ChangeLog (ChangeLog_Eng.txt, ChangeLog_Rus.txt)). 3. Also, ebuild should provide 'doc' USE flag. In addition to included to the package doc (OOoFBTools_Help.pdf) and examples (ExportToFB21_example-1.odt, ExportToFB21_example-2.odt) upstream provides two additional external docs (one English language and one Russian) with the same distributing issue. 4. At last, office-ext-r1 eclass installs _all_ extension files (including some win32 binaries, inoperable and not needed at all in Linux).
Also, in addition to LINGUAS handling, extension contain localized FictionBook2.1 style names for languages: be de en es fr it pl ru uk For now portage installs all of them: … /usr/lib64/libreoffice/share/extensions/OOoFBTools/styles/fb21_styles.ott /usr/lib64/libreoffice/share/extensions/OOoFBTools/styles/fb21_styles_be.ott … Ideally, this list also should be system locale's selective.
Created attachment 366410 [details] ooofbtools-2.25.ebuild with fixed SRC_URI I was confused by referencies on project's web-site. Fixing it.
Version added to cvs. 4) it installs exactly what is content of the extension. The extension is then wrongly created by the authors as it should contain only platform independent files. 3) it should not. We do not install localized docs that do not have english counterpart. 2) as per 3 1) as per 3
