From: Gary Thomas <gary@mlbassoc.com>
To: "Andreas Müller" <schnitzeltony@googlemail.com>,
"Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] python-pygtk: Restore pkg-config file
Date: Thu, 30 Oct 2014 09:39:21 -0600 [thread overview]
Message-ID: <54525BA9.9000606@mlbassoc.com> (raw)
In-Reply-To: <CALbNGRTQQTza3PftOobxDqMvJUGwsGKRAcRX49CXtzUeTOcSzQ@mail.gmail.com>
On 2014-10-30 09:26, Andreas Müller wrote:
> On Thu, Oct 30, 2014 at 1:57 PM, Burton, Ross <ross.burton@intel.com> wrote:
>>
>> On 28 October 2014 15:05, Gary Thomas <gary@mlbassoc.com> wrote:
>>>
>>> Some previous version of this recipe was errantly removing the
>>> pygtk-2.0.pc
>>> (pkg-config) file. This is needed for other packages to be able to build
>>> against this library.
>>
>>
>> It's deleting the code generator too. This entire recipe gives me the
>> heebie-jeebies...
>>
>> Ross
>>
> I have a similar patch in for very long time [1]. At the time of
> creation I ran several tests without suspicious results. The whole
> 'dirty fix #1' can go.
>
> Andreas
>
> [1] https://gitorious.org/schnitzeltony-oe-meta/oe-core/commit/dedf83428f297e9461f5c88c32c78192fa96585e
>
Wow, since Jan 2013 and no action?
Was this proposed to OE-core (i.e. sent to the list)?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2014-10-30 15:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 15:05 [PATCH] python-pygtk: Restore pkg-config file Gary Thomas
2014-10-30 12:57 ` Burton, Ross
2014-10-30 15:26 ` Andreas Müller
2014-10-30 15:39 ` Gary Thomas [this message]
2014-10-30 16:14 ` Andreas Müller
2014-10-30 17:28 ` Richard Purdie
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=54525BA9.9000606@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
--cc=schnitzeltony@googlemail.com \
/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