From: Phil Blundell <pb@pbcl.net>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] rootfs_ipk, image: Add debug capture support
Date: Fri, 26 Apr 2013 14:57:37 +0100 [thread overview]
Message-ID: <1366984657.14512.108.camel@phil-desktop.brightsign> (raw)
In-Reply-To: <517933DC.9080809@windriver.com>
On Thu, 2013-04-25 at 08:47 -0500, Mark Hatle wrote:
> 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.
I dunno. It seems a bit sad to force use of update-alternatives just to
deconflict the .debug data (since the binaries in question would never
be installed at the same time anyway), and in general it seems like we
want less update-alternatives rather than more of it.
But I guess that would indeed solve the problem and it's probably the
lowest-effort thing that does. So maybe that's the way ahead.
p.
next prev parent reply other threads:[~2013-04-26 14:15 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
2013-04-26 13:57 ` Phil Blundell [this message]
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=1366984657.14512.108.camel@phil-desktop.brightsign \
--to=pb@pbcl.net \
--cc=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