Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] omap-u-boot-utils: add new package
Date: Wed, 21 Sep 2011 15:00:40 +0200	[thread overview]
Message-ID: <4E79DFF8.6000506@lucaceresoli.net> (raw)
In-Reply-To: <20110919224432.705c22ac@skate>

Thomas,

Thomas Petazzoni wrote:
> Le Mon, 19 Sep 2011 16:53:26 +0200,
> Luca Ceresoli<luca@lucaceresoli.net>  a ?crit :
>
>> +config BR2_PACKAGE_HOST_OMAP_U_BOOT_UTILS
>> +	bool "omap-u-boot-utils"
>> +	help
>> +	  U-Boot Utilities for Texas Instrument's OMAP platforms.
>> +	  Say Y if you want these utilities on the development host.
>> +
>> +	  https://github.com/nmenon/omap-u-boot-utils
>
> I continue to disagree with the fact of adding an host utility in the
> Config.in menu, or at least not without a broader discussion about this.
>
> Since we have started to normalize the generation of host packages
> (late 2009/early 2010), we decided that host packages should *not*
> appear in the menuconfig, but that they rather should only be handled
> through make dependencies.

Sorry, I didn't know: I was not closely following the buildroot
development at that time.

 > If we decide to change this decision, we
> need to think about it globally, i.e what we want to do for *all* host
> packages and not only particular cases.
>
> I must admit there are other cases for which being able to show host
> packages to users would be useful. For example, on AT91 platforms,
> there is an host utility called SAM-BA which allows to reflash an AT91
> device through the USB device port. This host utility could be
> conveniently downloaded, extracted and installed into $(HOST_DIR) by
> Buildroot, but we have currently no way of doing this.
>
> Some thing for OpenOCD. Jean-Christophe has recently added support for
> it for the target, but being able to build OpenOCD on the host and
> install it in $(HOST_DIR) would also be useful for those of us who want
> to build ready-to-use development environments with Buildroot.
>
> Anyway, in the mean time, I'm NACKing those patches until a proper
> discussion has taken place, resulting in the definition of a solution
> that works for all host packages.

I understand. I just posted a v2 to have the trivial fixes and
improvements requested so far and stop thinking about them.

I'm going to start a new thread right now to open the discussion.

Luca

      reply	other threads:[~2011-09-21 13:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-13 17:19 [Buildroot] [PATCH 1/2] omap-u-boot-utils: add new package Luca Ceresoli
2011-09-13 17:19 ` [Buildroot] [PATCH 2/2] u-boot: build signed image for OMAP processors Luca Ceresoli
2011-09-13 18:14   ` Gustavo Zacarias
2011-09-14  8:39     ` Luca Ceresoli
2011-09-13 17:44 ` [Buildroot] [PATCH 1/2] omap-u-boot-utils: add new package Thomas Petazzoni
2011-09-14  8:58   ` Luca Ceresoli
2011-09-19 14:53 ` [Buildroot] [PATCH v2 " Luca Ceresoli
2011-09-19 14:53   ` [Buildroot] [PATCH v2 2/2] u-boot: build signed image for OMAP processors Luca Ceresoli
2011-09-19 20:44   ` [Buildroot] [PATCH v2 1/2] omap-u-boot-utils: add new package Thomas Petazzoni
2011-09-21 13:00     ` Luca Ceresoli [this message]

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=4E79DFF8.6000506@lucaceresoli.net \
    --to=luca@lucaceresoli.net \
    --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