#38871: tesseract @3.02.02 version upgrade
-------------------------+----------------------
Reporter: mdbecque@… | Owner: emer@…
Type: update | Status: closed
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: fixed | Keywords: haspatch
Port: tesseract |
-------------------------+----------------------
Changes (by ryandesign@…):
* status: new => closed
* resolution: => fixed
Comment:
The patch was reversed but that's easy to deal with.
Replying to [comment:13 emer@…]:
> I'm not sure if we still need the old patches. It builds on my machine
without them, but I forget exactly why we needed them, and I think it was
something I could not replicate. If someone could try that out, that'd be
cool.
The only reason we were patching configure.ac and running autoreconf was
to fix a failure when $CC has a space in it, e.g. when ccache is being
used (which it is on my system). Running autoreconf necessitated making
the empty m4 directory. This bug in the configure script is fixed in 3.02
so we no longer need this patch nor to run autoreconf nor to create the m4
directory.
The only reason we were patching strngs.h was to remove the UTF-8 byte
order marker from the file, which older GCC compilers failed on. In 3.02
there is no UTF-8 BOM on this file so we don't need to patch it.
There was a special-case section in the language subport code for dealing
with version 3.00 language files. Since the port now doesn't have any of
those anymore I removed the special-case code.
Some of the subports appear to conflict with one another. For example,
tesseract-eng fails to activate, saying:
{{{
Error: org.macports.activate for port tesseract-eng returned: Image error:
/opt/local/share/tessdata/eng.cube.params is being used by the active
tesseract-ara port. Please deactivate this port first, or use 'port -f
activate tesseract-eng' to force the activation.
}}}
Why does tesseract-ara install files for other languages?
{{{
$ port cont tesseract-ara
Port tesseract-ara contains:
/opt/local/share/tessdata/ara.cube.bigrams
/opt/local/share/tessdata/ara.cube.fold
/opt/local/share/tessdata/ara.cube.lm
/opt/local/share/tessdata/ara.cube.nn
/opt/local/share/tessdata/ara.cube.params
/opt/local/share/tessdata/ara.cube.size
/opt/local/share/tessdata/ara.cube.word-freq
/opt/local/share/tessdata/ara.traineddata
/opt/local/share/tessdata/eng.cube.params
/opt/local/share/tessdata/fra.cube.params
/opt/local/share/tessdata/hin.cube.params
/opt/local/share/tessdata/ita.cube.params
/opt/local/share/tessdata/rus.cube.params
/opt/local/share/tessdata/spa.cube.params
}}}
Similarly, tesseract-fra fails to activate:
{{{
Error: org.macports.activate for port tesseract-fra returned: Image error:
/opt/local/share/tessdata/dan-frak.traineddata is being used by the active
tesseract-dan port. Please deactivate this port first, or use 'port -f
activate tesseract-fra' to force the activation.
}}}
And so on. I've committed the port as is in r112497 but we need to figure
out how we want to handle this: either marking the ports as conflicting
with one another, or making them not conflict. I'll file a new ticket.
--
Ticket URL: <https://trac.macports.org/ticket/38871#comment:19>
MacPorts <http://www.macports.org/>
Ports system for OS X