From: wenzong fan <wenzong.fan@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] udev: ship source files to related dbg package
Date: Fri, 8 Nov 2013 16:10:23 +0800 [thread overview]
Message-ID: <527C9C6F.4050509@windriver.com> (raw)
In-Reply-To: <CAJTo0LZHwv3jbAP_utqA-RUALdE_R7OtpUQnzaWU67qup47fHQ@mail.gmail.com>
On 11/07/2013 07:12 PM, Burton, Ross wrote:
> On 7 November 2013 11:03, <wenzong.fan@windriver.com> wrote:
>> From: Wenzong Fan <wenzong.fan@windriver.com>
>>
>> Just ship these sources to their own dbg packages instead of udev-dbg:
>>
>> libudev* -> libudev-dbg
>> gudev* -> libgudev-dbg
>> others -> udev-dbg
>
> Why do this? Multiple -dbg packages could make sense in a recipe
> which builds a multi-gigabyte -dbg package (such as webkit) but what's
> the rationale for doing this in udev?
Actually I don't know clear about why it needs three -dbg packages,
looks they have been there since very early commits of udev. I suspect
that udev/libudev/libgudev are independent each other, so they are
shipped into different packages (base/-dev/-dbg). This patch only ships
their source code to -dbg packages accordingly.
Thanks
Wenzong
>
> Ross
>
>
next prev parent reply other threads:[~2013-11-08 8:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 11:03 [PATCH 0/1] udev: ship source files to related dbg package wenzong.fan
2013-11-07 11:03 ` [PATCH 1/1] " wenzong.fan
2013-11-07 11:12 ` [PATCH 0/1] " Burton, Ross
2013-11-08 8:10 ` wenzong fan [this message]
2013-11-08 8:18 ` Richard Purdie
2013-11-08 8:26 ` wenzong fan
2013-11-11 10:13 ` 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=527C9C6F.4050509@windriver.com \
--to=wenzong.fan@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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