Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] udev: remove libudev-dbg and libgudev-dbg
Date: Mon, 11 Nov 2013 10:05:06 -0600	[thread overview]
Message-ID: <52810032.3020608@windriver.com> (raw)
In-Reply-To: <cover.1384164392.git.wenzong.fan@windriver.com>

On 11/11/13, 4:10 AM, wenzong.fan@windriver.com wrote:
> From: Wenzong Fan <wenzong.fan@windriver.com>
>
> We don't support multiple -dbg packages, so just remove the libudev-dbg,
> libgudev-dbg and put all debug stuffs to 'udev-dbg'.

I'm a bit confused, we do support package that want to provide multiple -dbg 
files to generate them.

This way large recipes that provide lots of different bits of functionality can 
no only segment the packages they create, but keep the side of the -dbg 
information reasonable as well.  (It's not all that commonly used, but it does 
work with the IMAGE_FEATURES 'dbg-pkgs'.)

What issue was being solved by combining the two items back into one?

--Mark

> The following changes since commit 4fdc3d77d4a875b7236536bf78849a4d1f6a7449:
>
>    kbd: Fix stdarg related errors on uclibc (2013-11-08 17:31:36 +0000)
>
> are available in the git repository at:
>
>    git://git.pokylinux.org/poky-contrib wenzong/udev-remove-dbg
>    http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=wenzong/udev-remove-dbg
>
> Wenzong Fan (1):
>    udev: remove libudev-dbg and libgudev-dbg
>
>   meta/recipes-core/udev/udev.inc |    6 ++----
>   1 file changed, 2 insertions(+), 4 deletions(-)
>



  parent reply	other threads:[~2013-11-11 16:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-11 10:10 [PATCH 0/1] udev: remove libudev-dbg and libgudev-dbg wenzong.fan
2013-11-11 10:10 ` [PATCH 1/1] " wenzong.fan
2013-11-11 16:05 ` Mark Hatle [this message]
2013-11-12  1:53   ` [PATCH 0/1] " wenzong fan
2013-11-12  7:47   ` Richard Purdie
2013-11-14  2:56     ` wenzong fan

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=52810032.3020608@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