From: Mike Crowe <mac@mcrowe.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] libc-common: Apply Debian-naming to libc debug symbols too
Date: Mon, 19 Mar 2012 13:37:31 +0000 [thread overview]
Message-ID: <20120319133731.GA4473@mcrowe.com> (raw)
In-Reply-To: <511DBFC2-F4AF-4C39-91D2-F59F686F21F5@dominion.thruhere.net>
Op 16 mrt. 2012, om 17:32 heeft Mike Crowe het volgende geschreven:
>>>> diff --git a/meta/classes/libc-common.bbclass b/meta/classes/libc-common.bbclass
>>>> index 962f205..d0c1ab4 100644
>>>> --- a/meta/classes/libc-common.bbclass
>>>> +++ b/meta/classes/libc-common.bbclass
>>>> @@ -27,4 +27,5 @@ python populate_packages_prepend () {
>>>> bpn = d.getVar('BPN', True)
>>>> d.setVar('PKG_'+bpn, 'libc6')
>>>> d.setVar('PKG_'+bpn+'-dev', 'libc6-dev')
>>>> + d.setVar('PKG_'+bpn+'-dbg', 'libc6-dbg')
>>>> }
On Fri, Mar 16, 2012 at 08:39:00PM +0100, Koen Kooi wrote:
>>> Missing PR bump
Op 19 mrt. 2012, om 12:52 heeft Mike Crowe het volgende geschreven:
>> On eglibc?
On Mon, Mar 19, 2012 at 12:59:53PM +0100, Koen Kooi wrote:
> On everything that uses that class.
OK.
>>> and broken upgrade path.
>> I'm having trouble coming up with a way to solve that. I think the
>> libc6-dbg package needs to RPROVIDE, RREPLACE and RCONFLICT with
>> libc-dbg but if I add the following:
>>
>> d.setVar('RPROVIDES_' + bpn + '-dbg', bpn + '-dbg')
>> d.setVar('RCONFLICTS_' + bpn + '-dbg', bpn + '-dbg')
>> d.setVar('RREPLACES_' + bpn + '-dbg', bpn + '-dbg')
> Does d.setVar('RREPLACES_' + bpn + '-dbg', 'libc-dbg') work?
It seems to. Do I just need to set RREPLACES or all three?
Thanks.
Mike.
next prev parent reply other threads:[~2012-03-19 13:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 16:32 [PATCH] libc-common: Apply Debian-naming to libc debug symbols too Mike Crowe
2012-03-16 19:39 ` Koen Kooi
2012-03-19 11:52 ` Mike Crowe
2012-03-19 11:59 ` Koen Kooi
2012-03-19 13:37 ` Mike Crowe [this message]
2012-03-20 17:27 ` Mike Crowe
2012-03-19 12:03 ` Martin Jansa
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=20120319133731.GA4473@mcrowe.com \
--to=mac@mcrowe.com \
--cc=openembedded-core@lists.openembedded.org \
/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.