| 1 |
Hi, |
| 2 |
|
| 3 |
the OCR software tesseract has many different plugins for |
| 4 |
language packs used for OCR for different languages. The ebuild |
| 5 |
uses the LINGUAS variable to pass the choice of which packages to |
| 6 |
install to the user. |
| 7 |
|
| 8 |
A reverse dependency is app-text/pdfsandwich which roughly puts |
| 9 |
OCR'ed text in a scanned pdf. Since it uses tesseract it |
| 10 |
supports exactly those languages that tesseract supports. |
| 11 |
|
| 12 |
Should its ebuild have LINGUAS use flags and then depend on |
| 13 |
tesseract with at least those flags set? |
| 14 |
|
| 15 |
While it seems consistent to put the LINGUAS choice in the most |
| 16 |
user facing package, in this case I would actually not put it in |
| 17 |
here. It would introduces a point of failure and maintenance |
| 18 |
work for the each tesseract upgrade (since the language set |
| 19 |
slightly changes from time to time). A typical user would set |
| 20 |
LINGUAS in her make.conf anyway. In this case the same choice |
| 21 |
applies to both packages anyway. Maybe an einfo is sufficient to |
| 22 |
inform the user it? |
| 23 |
|
| 24 |
Cheers, |
| 25 |
Thomas |
| 26 |
|
| 27 |
|
| 28 |
|
| 29 |
-- |
| 30 |
Thomas Kahle |
| 31 |
http://dev.gentoo.org/~tomka/ |
Archives