Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/2] zbar: new package
Date: Thu, 29 Oct 2015 10:21:29 +0000	[thread overview]
Message-ID: <5631F329.6060105@imgtec.com> (raw)
In-Reply-To: <1446100633-23719-1-git-send-email-sv99@inbox.ru>

Dear Viacheslav Volkov,

sorry, one more comment on this.

On 10/29/2015 06:37 AM, Viacheslav Volkov wrote:
> +ZBAR_VERSION = 854a5d97059e395807091ac4d80c53f7968abb8f
> +ZBAR_SITE = $(call github,ZBar,Zbar,$(ZBAR_VERSION))

There are released tarballs that can be downloaded from the official
ZBar website. Why don't you use them instead of GitHub? We normally
prefer released tarballs unless there is a good reason to not do it.

In case there is such a good reason to not use the released tarball, why
do you use the GitHub mirror? It looks like the official ZBar repository
is the Mercurial one:

http://sourceforge.net/p/zbar/code/ci/default/tree/

I don't know the opinion of other developers, but I would prefer to use
the official repository instead of a mirror when possible. So, my order
of preference would be:

1st - released tarballs
2nd - official repository
3rd - mirror

Regards,

Vincent.

  parent reply	other threads:[~2015-10-29 10:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29  6:37 [Buildroot] [PATCH v3 1/2] zbar: new package Viacheslav Volkov
2015-10-29 10:09 ` Vicente Olivert Riera
2015-10-29 10:21 ` Vicente Olivert Riera [this message]
2015-10-29 11:36 ` Martin Bark
  -- strict thread matches above, loose matches on Subject: below --
2015-10-28 14:17 Viacheslav Volkov
2015-10-29  5:39 ` Yegor Yefremov

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=5631F329.6060105@imgtec.com \
    --to=vincent.riera@imgtec.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