Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Chong Lu <Chong.Lu@windriver.com>
To: Henning Heinold <henning@itconsulting-heinold.de>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] perf: split package
Date: Thu, 17 Jul 2014 15:52:45 +0800	[thread overview]
Message-ID: <53C780CD.3030903@windriver.com> (raw)
In-Reply-To: <20140717070406.GA2666@mail.itconsulting-heinold.de>


On 07/17/2014 03:04 PM, Henning Heinold wrote:
> On Thu, Jul 17, 2014 at 02:58:46PM +0800, Chong Lu wrote:
>> On 07/17/2014 10:13 AM, Bruce Ashfield wrote:
>>> On Wed, Jul 16, 2014 at 9:43 PM, Chong Lu <Chong.Lu@windriver.com> wrote:
>>>> On 07/16/2014 09:04 PM, Bruce Ashfield wrote:
>>>>> On Wed, Jul 16, 2014 at 4:00 AM, Chong Lu <Chong.Lu@windriver.com> wrote:
>>>>>> Fix incorrect paths to split perf package.
>>>>> Can you elaborate here ? This commit message doesn't really tell us much.
>>>>> Why is the current split incorrect ? What is the symptom and result of the
>>>>> incorrect split ? Are the package contents the same after this change ?
>>>>>
>>>>> Bruce
>>>> Hi Bruce,
>>>>
>>>> Currently, perf can't split to perf-archive, perf-tests, perf-python and
>>>> perf-perl.
>>>> All files are included in perf package. For example, like perf-tests
>>>> package:
>>>> It generates files in '${exec_prefix}/libexec/perf-core/tests', not in
>>>> '${libdir}/perf/perf-core/tests'.
>>>> So I change the files paths to make split successfully.
>>> But that means, whether or not we like it, anything using perf has been using
>>> those "non splits" and getting everything when perf is installed.
>>>
>>> It's also might be in order to make the main perf package RDEPEND on
>>> the other three, to keep it consistent. Make it a ?= so it can be overridden,
>>> and then we can age it out over time.
>>>
>>> Bruce
>> Do you mean we should set RDEPENDS like:
>>      RDEPENDS_${PN} ?= "${PN}-archive ${PN}-tests ${PN}-python ${PN}-perl"
>>
>> In perf.bb file, we have RDEPENDS_${PN} += "elfutils", so I think we
>> should use
>>      RDEPENDS_${PN} += "${PN}-archive ${PN}-tests ${PN}-python ${PN}-perl"
>> to keep it consistent. Do you agree?
>>
>> Or, we can also revert following commit to make all files in perf package.
>>      commit 36c3e923df85e685b707fe6bd84b053a5e366fe4
>>      Author: Henning Heinold <henning@itconsulting-heinold.de>
>>      Date:   Mon Jun 9 23:21:29 2014 +0200
>>
>>          perf: split packging
>>
>> Best Regards
>> Chong
> Please do not destroy the following use case, which is using perf top
> WIHTOUT installing perl or python.
>
> Bye Henning
Hi Henning,

perf can't split to perf-archive, perf-tests, perf-python and perf-perl 
from your patch.
Currently, all files are in perf package.

BR
Chong



  reply	other threads:[~2014-07-17  7:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-16  8:00 [PATCH 0/1] perf: split package Chong Lu
2014-07-16  8:00 ` [PATCH 1/1] " Chong Lu
2014-07-16 13:04   ` Bruce Ashfield
2014-07-17  1:43     ` Chong Lu
2014-07-17  2:13       ` Bruce Ashfield
2014-07-17  6:58         ` Chong Lu
2014-07-17  7:04           ` Henning Heinold
2014-07-17  7:52             ` Chong Lu [this message]
2014-07-17 13:22           ` Bruce Ashfield

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=53C780CD.3030903@windriver.com \
    --to=chong.lu@windriver.com \
    --cc=henning@itconsulting-heinold.de \
    --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