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] htop: new package
Date: Fri, 14 Jan 2011 08:59:41 +0100	[thread overview]
Message-ID: <20110114085941.6df4841d@surf> (raw)
In-Reply-To: <9AC3F0E75060224C8BBC5BA2DDC8853A1EE63C42@EXV1.corp.adtran.com>

Hello Andy,

On Wed, 12 Jan 2011 15:15:30 -0600
ANDY KENNEDY <ANDY.KENNEDY@adtran.com> wrote:

> The following adds support for version 0.8.3 of htop.  0.9 is the
> latest, however, is dependant on backtrace.  The next version is to
> remove the hard dependencies of backtrace and make it a compile-time
> check.

Your patch is word-wrapped. Could you check your e-mail
client configuration ? You should probably try git send-email, as this
will guarantee that your patches will make it properly to the list,
without being word-wrapped or damaged in anyway by the mail client
you're using.

> Signed-off-by: Andy Kennedy <andy.kennedy@adtran.com>
> ---
> diff -Naur a/package/htop/Config.in b/package/htop/Config.in
> --- a/package/htop/Config.in    1969-12-31 18:00:00.000000000 -0600
> +++ b/package/htop/Config.in    2011-01-11 15:16:01.000000000 -0600
> @@ -0,0 +1,9 @@
> +config BR2_PACKAGE_HTOP
> +       bool "htop"
> +       select BR2_PACKAGE_NCURSES
> +       select UCLIBC_HAS_BACKTRACE if BR2_TOOLCHAIN_BUILDROOT

We can't do that. UCLIBC_HAS_BACKTRACE does not exist in the current
version of Buildroot. Probably a left over from the packaging of htop
0.9, which requires backtrace support.

However, even when you'll package htop 0.9, the current policy is not
to do something like selecting a given UCLIBC option. We either :

 *) Enable the needed option in our default uClibc build, if the
    footprint impact is reasonable and the option is sufficiently useful
    for different packages.

 *) Or add a comment in the package help in Config.in stating that the
    package would not build with the default uClibc configuration.

None of those options are perfect, but we'd like to avoid adding dozens
and dozens of options at the Buildroot level to tweak every possible
option of uClibc.

> diff -Naur a/package/htop/htop-cross-no-proc-check.patch
> b/package/htop/htop-cross-no-proc-check.patch
> --- a/package/htop/htop-cross-no-proc-check.patch       1969-12-31
> 18:00:00.000000000 -0600
> +++ b/package/htop/htop-cross-no-proc-check.patch       2011-01-12
> 14:51:53.000000000 -0600

Patch lacks a description of why it is needed and the Signed-off-by
line.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2011-01-14  7:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-12 21:15 [Buildroot] [PATCH] htop: new package ANDY KENNEDY
2011-01-14  7:59 ` Thomas Petazzoni [this message]
2011-01-14 16:14   ` ANDY KENNEDY
2011-01-14 17:14     ` Thomas Petazzoni
  -- strict thread matches above, loose matches on Subject: below --
2011-01-14 22:54 Andy Kennedy
2011-01-14 22:55 ` ANDY KENNEDY
2011-01-14 23:38 Andy Kennedy

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=20110114085941.6df4841d@surf \
    --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