Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH V2] openocd: fetch package from git repository and update version
Date: Tue, 28 Feb 2012 20:46:40 +0000	[thread overview]
Message-ID: <201202282046.41124.arnout@mind.be> (raw)
In-Reply-To: <20120226043705.GD10670@game.jcrosoft.org>

On Sunday 26 February 2012 04:37:06 Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 00:06 Sun 26 Feb     , Alexandre Pereira da Silva wrote:
[snip]
> > The openocd release is 6 months old and they made many improvements
> > since then. And I don't see any plans for them to release a new
> > version any time soon.
> I will release a new version of openocd in time, today the current version is
> not stable enough

 That's a good reason to NACK the use of the git commit.  Thank you for
the explanation, Jean-Christophe.


> > This is a special package like u-boot and the kernel because in many
> > occasions you have to tweak the package to suit your own hardware.
> The NACK stand
> 
> You can do it for your local but for mainline no, barebox/ u-boot, linux are
> based on release

 Difference being that all of those release quite frequently :-)

> > Other option would be to use 0.5.0 version from git, so people who run
> > into this kind of issue, can override the version more easily.
> NACK
> 
> git is very slow to download it's NOT an option at all for default version

 Good point as well.

 With the need for local patches and the occasional local need for a git 
version rather than a release, you could consider adding git and patches
support to openocd's Config.in, like is the case for U-Boot and linux.


> > Another comment on this issue is about git submodule fetching. Do you
> > think that could be useful to other packages? If so, I can prepare a
> > new patch to fetch all submodules, if any.

 I'm not too keen on that.  Although I could be convinced.  Such a
feature would definitely have to be verified with all current git-based
packages.

 Regards,
 Arnout

 
-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2012-02-28 20:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-24 18:19 [Buildroot] [PATCH] openocd: fetch package from git repository and update version Alexandre Pereira da Silva
2012-02-24 19:01 ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-24 21:31   ` [Buildroot] [PATCH V2] " Alexandre Pereira da Silva
2012-02-25  3:33     ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-25 15:31       ` Arnout Vandecappelle
2012-02-26  3:06         ` Alexandre Pereira da Silva
2012-02-26  4:37           ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-28 20:46             ` Arnout Vandecappelle [this message]
2012-02-26  4:39         ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-26  4:40           ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-28 13:34           ` Thomas Petazzoni
2012-02-28 20:44             ` Peter Korsgaard
2012-02-29 14:42             ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-29 17:20               ` Alexandre Pereira da Silva
2012-03-05 10:54                 ` Thomas Petazzoni
2012-02-29 18:15               ` Yann E. MORIN

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=201202282046.41124.arnout@mind.be \
    --to=arnout@mind.be \
    --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