Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] tesseract-ocr: new package
Date: Mon, 20 Mar 2017 00:03:32 +0100	[thread overview]
Message-ID: <20170320000332.6e5e9983@free-electrons.com> (raw)
In-Reply-To: <ecfe5b92-0800-cb5c-3f22-53448c1255f9@mind.be>

Hello,

On Mon, 20 Mar 2017 00:00:27 +0100, Arnout Vandecappelle wrote:

> >  * Since the list of languages is quite long, having an explicit option
> >    for each of them is a bit annoying. So I looked into turning your
> >    one-option-per-language idea into a single option with a space
> >    separated list of languages. Except that we anyway need to have the
> >    hash file for each language in tesseract-ocr.hash.  
> 
>  That's why we have BR_NO_CHECK_HASH_FOR, no?

True. But then we don't check hashes for stuff downloaded through
Github, which potentially could change (hence the reason why I'm also
suggesting to have a package that downloads all of the tessdata
package, but it's huge).

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-03-19 23:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-19  8:07 [Buildroot] [PATCH v2 0/2] Introducing tesseract OCR engine Gilles Talis
2017-03-19  8:07 ` [Buildroot] [PATCH v2 1/2] leptonica: new package Gilles Talis
2017-03-19 13:51   ` Thomas Petazzoni
2017-03-20 15:05   ` Peter Korsgaard
2017-03-21  7:37     ` Gilles Talis
2017-03-19  8:07 ` [Buildroot] [PATCH v2 2/2] tesseract-ocr: " Gilles Talis
2017-03-19 13:54   ` Thomas Petazzoni
2017-03-19 23:00     ` Arnout Vandecappelle
2017-03-19 23:03       ` Thomas Petazzoni [this message]
2017-03-20  8:10         ` Gilles Talis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170320000332.6e5e9983@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox