From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2 4/4] iw: pkg-config nitpicking
Date: Fri, 28 Sep 2012 16:12:32 +0200 [thread overview]
Message-ID: <20120928161232.0dd7a779@skate> (raw)
In-Reply-To: <5064D2BA.4050102@zacarias.com.ar>
On Thu, 27 Sep 2012 19:27:06 -0300, Gustavo Zacarias wrote:
> On 09/27/12 18:40, Arnout Vandecappelle wrote:
> > Doesn't removing GIT_DIR break version.sh?
>
> Oh yes it does on dirty, my bad for being to 'dd' happy.
> I'll resend the whole set once it's decided what to do about pkg-config.
> IMHO host-pkg-config can be killed with fire, no need to duplicate it.
> pkg-config might be deprecated as per the usual rite, though it's
> duplicate functionality and could be just killed being a piggy with glib
> deps :)
I agree that we don't need a deprecation period for pkg-config. It is
just an internal build dependency, nobody cares about it, especially if
there is a drop-in replacement for it.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2012-09-28 14:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 10:48 [Buildroot] [PATCHv2 1/4] pkgconf: new package Gustavo Zacarias
2012-09-26 10:48 ` [Buildroot] [PATCHv2 2/4] packages: switch to pkgconf Gustavo Zacarias
2012-09-26 10:48 ` [Buildroot] [PATCHv2 3/4] pkg-config: remove package Gustavo Zacarias
2012-09-26 10:48 ` [Buildroot] [PATCHv2 4/4] iw: pkg-config nitpicking Gustavo Zacarias
2012-09-27 21:40 ` Arnout Vandecappelle
2012-09-27 22:27 ` Gustavo Zacarias
2012-09-28 14:12 ` Thomas Petazzoni [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=20120928161232.0dd7a779@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.