Linux Media Controller development
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: linux-media@vger.kernel.org, dougsland@redhat.com
Subject: [ANN] added Zbar repository at linuxtv.org
Date: Mon, 27 Mar 2017 12:48:13 -0300	[thread overview]
Message-ID: <20170327124813.0713fabb@vento.lan> (raw)

Hi,

Just to let you know, I added today a repository at linuxtv.org with a fork
of the ZBar bar code reader.

The Zbar tool is an interesting V4L2 application, as it reads code bars
from several different codes from a webcam (or a scanned file).

The original page for this project is at http://zbar.sourceforge.net/

Unfortunately, it doesn't have maintenance there, since 2012. This was
its last commit upstream:

	changeset:   362:38e78368283d
	tag:         tip
	user:        spadix@users.sourceforge.net
	date:        Sun Oct 14 23:02:08 2012 -0700
	summary:     Added tag iPhoneSDK-1.3.1 for changeset 5eb3c8786845

At least on Fedora, upstream version doesn't even compile 
without fixing configure.ac to work with modern automake tools.

As Douglas and I are maintaining this package under Fedora, and
I had to write some other patches on Fedora, in order to migrate it
to Qt5, I'm opting to keep a fork of its patched version at
linuxtv.org.

The version there is basically the original development tree,
converted from Mercurial to git. For the few patches at the
Fedora packaging repository, I added a commit, in order to 
preserve credits for the authors of the changes there.

Please notice that I don't have currently any plans to do any
development on it, doing mainly bug fixes as required to keep it 
building and working.

So, if anyone is interested on keeping maintaining it, please
ping me. Feel free to also send patches for it to linux-media ML.

Thanks,
Mauro


[1] I got the zbar patch credits by running:

	$ git log zbar*.patch

Please notice that this doesn't cover other patches that were there
at the repository, but got removed.

	Author: Douglas Schilling Landgraf <dougsland@redhat.com>
	Date:   Mon Aug 17 10:37:15 2015 -0300
	    zbar - zbar-0.10-25
    
	    Added:
	       zbar_configure_ac_use_m4_pattern_allow.patch
    
	    Removed:
	       zbar_dont_user_reserved_dprintf.patch

	Author: Douglas Schilling Landgraf <dougsland@redhat.com>
	Date:   Sat Jun 6 20:46:10 2015 -0300

    Patch: use REQBUFS properly

	Author: Mauro Carvalho Chehab <mchehab@redhat.com>
	Date:   Fri Feb 22 08:26:55 2013 -0300

	    Update to the very latest version of zbar
    
	    zbar was using a 2010 snapshot of its hg tree.
	    Take a new snapshot to get zbar's improvements.

	Author: Mauro Carvalho Chehab <mchehab@redhat.com>
	Date:   Sat Dec 25 10:57:22 2010 -0200

	    Only use emulated formats if real formats aren't supported
    
	    Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>

	Author: Rafael Azenha Aquini <aquini@fedoraproject.org>
	Date:   Sat Dec 18 14:43:10 2010 -0200
	
	    - Update it to the newest version available at zbar git directory
	    - Use libv4l to communicate with video devices

             reply	other threads:[~2017-03-27 15:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27 15:48 Mauro Carvalho Chehab [this message]
2017-03-27 16:07 ` [ANN] added Zbar repository at linuxtv.org Douglas Landgraf

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=20170327124813.0713fabb@vento.lan \
    --to=mchehab@s-opensource.com \
    --cc=dougsland@redhat.com \
    --cc=linux-media@vger.kernel.org \
    /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