From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] rxvt-unicode: new package
Date: Fri, 4 Jan 2013 17:23:12 +0100 [thread overview]
Message-ID: <20130104172312.5237b902@skate> (raw)
In-Reply-To: <50E6F52F.5040204@petroprogram.com>
Dear Stefan Fr?berg,
On Fri, 04 Jan 2013 17:28:47 +0200, Stefan Fr?berg wrote:
> So for example in this elfutils case it should have been one big patch
> (because all those individual
> *.patch files are really needed to make it build).
>
> And any extra patches in that series would just add features
> (like BR2_PACKAGE_ELFUTILS_ZLiB_SUPPORT) or fix something ?
>
> In other words, first patch is the buildable core and everything else
> optional ?
Yes, we could summarize it this way.
Or, as I said, since the biggest problem with elfutils is uClibc
support, the first patch could have added a glibc-only elfutils (which
proper depends on) and then a second patch could add the necessary
additional crap to make it uClibc friendly.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-01-04 16:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 18:45 [Buildroot] [PATCH v2 1/2] rxvt-unicode: new package Stefan Fröberg
2012-12-27 18:45 ` [Buildroot] [PATCH v2 2/2] " Stefan Fröberg
2013-01-03 23:27 ` Thomas Petazzoni
2013-01-04 14:42 ` Stefan Fröberg
2013-01-04 15:03 ` Thomas Petazzoni
2013-01-04 15:28 ` Stefan Fröberg
2013-01-04 16:23 ` Thomas Petazzoni [this message]
2013-01-03 23:25 ` [Buildroot] [PATCH v2 1/2] " Thomas Petazzoni
2013-01-04 14:31 ` Stefan Fröberg
2013-08-13 22:07 ` Thomas Petazzoni
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=20130104172312.5237b902@skate \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.