Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] dbus-cpp: new package
Date: Thu, 26 Dec 2013 12:43:22 -0300	[thread overview]
Message-ID: <52BC4E9A.9050303@zacarias.com.ar> (raw)
In-Reply-To: <20131226162407.2debd602@skate>

On 12/26/2013 12:24 PM, Thomas Petazzoni wrote:

> Dear Gustavo Zacarias,
> 
> On Thu, 26 Dec 2013 12:00:26 -0300, Gustavo Zacarias wrote:
>> D-Bus C++ bindings, closes bug #65.
> 
> Wow, impressive, you even go to improvement bugs, and fix them!

Yeah, that number was nagging me, a 2-digit when we are on 4-digit bugs :P
Some people want to lower the patchwork patch count, i also look at bugs ;)

> I'm not a big fan when building one package requires poking into the
> source/build tree of another package (even if it's the host variant of
> the same package). Installing the host dbus-cpp into $(HOST_DIR) isn't
> sufficient to build the target dbus-cpp?

Me neither, the problem is patching it (bin/lib separately, ditching the
src/.libs & other references) won't be upstreamable since the option is
right there now and i don't think upstream will want a variation on the
subject.
It's doable but not upstreamable i think, what do we prefer?
Regards.

  reply	other threads:[~2013-12-26 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-26 15:00 [Buildroot] [PATCH] dbus-cpp: new package Gustavo Zacarias
2013-12-26 15:24 ` Thomas Petazzoni
2013-12-26 15:43   ` Gustavo Zacarias [this message]
2014-01-05 10:24     ` Peter Korsgaard

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=52BC4E9A.9050303@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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