From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] rootfs_ipk, image: Add debug capture support
Date: Thu, 25 Apr 2013 08:47:08 -0500 [thread overview]
Message-ID: <517933DC.9080809@windriver.com> (raw)
In-Reply-To: <1366888374.14512.78.camel@phil-desktop.brightsign>
On 4/25/13 6:12 AM, Phil Blundell wrote:
> On Tue, 2012-10-02 at 12:38 +0100, Richard Purdie wrote:
>> On Tue, 2012-10-02 at 12:15 +0100, Phil Blundell wrote:
>>> On Tue, 2012-10-02 at 12:12 +0100, Richard Purdie wrote:
>>>> Hasn't Paul added a general mechanism for doing this so we could add
>>>> this feature a level higher so that it could be used by all packaging
>>>> formats?
>>>
>>> Ah, possibly. I'll have a look. Can you give me a pointer to the
>>> mechanism you were thinking of?
>>
>> Something like IMAGE_FEATURES += "dbg-pkgs" should trigger the addition
>> of dbg packages.
>
> I've somewhat belatedly gotten around to using this and encountered a
> couple of issuettes:
>
> 1. There was a spurious-looking RRECOMMENDS_${PN}-dbg in bitbake.conf
> which was causing ${PN} to be dragged into the image whenever ${PN}-dbg
> was installed. This is undesirable because it means that, for example,
> any image which includes sysvinit-pidof will end up installing sysvinit
> and this might cause quite drastic changes to the behaviour of the
> resulting image.
>
> 2. Having fixed the above I'm now left with a couple of file conflicts
> in the -dbg packages. For example, sysvinit and util-linux both
> ship /sbin/sulogin and so sysvinit-dbg and util-linux-dbg both want to
> install /sbin/.debug/sulogin. This is unfortunate if you have an image
> which uses, say, sysvinit-pidof and util-linux-blkid.
Is this a problem that they should have used the update-alternatives for
sulogin? (Sounds like it might be a security issue though...) This would avoid
the .debug conflict.
--Mark
> I'm not quite sure what the right way to fix (2) is. I suppose in an
> ideal world the -dbg packages would be separated in the same way the
> parent binary packages are, but that doesn't look entirely
> straightforward to arrange.
>
> p.
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2013-04-25 14:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 9:20 [PATCH] rootfs_ipk, image: Add debug capture support Phil Blundell
2012-10-02 11:12 ` Richard Purdie
2012-10-02 11:15 ` Phil Blundell
2012-10-02 11:38 ` Richard Purdie
2012-10-02 13:42 ` Otavio Salvador
2012-10-02 13:51 ` Phil Blundell
2012-10-02 13:53 ` Otavio Salvador
2012-10-02 13:52 ` Martin Ertsås
2012-10-02 13:59 ` Otavio Salvador
2012-10-02 13:57 ` Martin Ertsås
2012-10-02 14:02 ` Otavio Salvador
2012-10-02 13:50 ` Phil Blundell
2013-04-25 11:12 ` Phil Blundell
2013-04-25 11:21 ` Martin Jansa
2013-04-25 13:47 ` Mark Hatle [this message]
2013-04-26 13:57 ` Phil Blundell
2013-04-26 14:16 ` Mark Hatle
2013-04-26 14:27 ` Phil Blundell
2013-04-26 14:39 ` Mark Hatle
2013-04-26 14:41 ` Phil Blundell
2013-04-26 14:50 ` Otavio Salvador
2013-04-26 16:05 ` Mark Hatle
2013-04-27 21:15 ` Chris Larson
2013-04-29 20:10 ` Debug Packaging (was: rootfs_ipk, image: Add debug capture support) Richard Purdie
2013-04-30 10:45 ` Phil Blundell
2013-04-30 15:24 ` Debug Packaging Mark Hatle
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=517933DC.9080809@windriver.com \
--to=mark.hatle@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox