All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Felipe Tonello <eu@felipetonello.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] valgrind: added perl dependency
Date: Wed, 26 Jun 2013 13:35:57 -0700	[thread overview]
Message-ID: <51CB50AD.2060008@linux.intel.com> (raw)
In-Reply-To: <CAGrhNMzXiTRTt=9wmYH0Bu4TsN3N82nkrERLmXAd-bBWH1U=iQ@mail.gmail.com>

On 06/26/2013 11:39 AM, Felipe Tonello wrote:
> Should I send another patch?
>

I think that Khem pointed out it should be an RDEPENDS not DEPENDS and 
you can drop the PR bump.

Sau!

> On Tue, Jun 11, 2013 at 12:36 AM, Khem Raj <raj.khem@gmail.com> wrote:
>> On Fri, Jun 7, 2013 at 11:37 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
>>> On Fri, Jun 07, 2013 at 10:51:14AM -0700, Felipe Tonello wrote:
>>>> I got this:
>>>>
>>>> valgrind/usr/bin/ms_print
>>>> 1:#! /usr/bin/perl
>>>>
>>>> valgrind/usr/bin/cg_diff
>>>> 1:#! /usr/bin/perl
>>>>
>>>> valgrind/usr/bin/cg_annotate
>>>> 1:#! /usr/bin/perl
>>>>
>>>> valgrind/usr/bin/callgrind_annotate
>>>> 1:#! /usr/bin/perl -w
>>>>
>>>> valgrind/usr/bin/callgrind_control
>>>> 1:#! /usr/bin/perl -w
>>>>
>>>> valgrind-doc/usr/share/doc/valgrind/html/manual-core.html
>>>> 165:<code class="filename">/usr/bin/perl</code>, or whatever interpreter
>>>>
>>>> valgrind-doc/usr/share/doc/valgrind/valgrind_manual.ps
>>>> 55978:(/usr/bin/perl) 77.7083 Tj
>>>>
>>>> Do you know if these "binaries" are part of the main package or can be
>>>> extra? I'm not that familiar with valgrind.
>>>
>>> Neither am I, but from filenames I would guess they are not mandatory to
>>> run valgrind binary, hopefully someone who is using valgrind daily will
>>> respond soon...
>>>
>>
>>
>> they are fine with valgrind package itself. although its a rdepend and
>> not depend
>>
>>
>>> --
>>> Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com
>>>
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>


  reply	other threads:[~2013-06-26 20:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-07 17:35 [PATCH] valgrind: added perl dependency eu
2013-06-07 17:42 ` Martin Jansa
2013-06-07 17:43   ` Martin Jansa
2013-06-07 17:47   ` Felipe Tonello
2013-06-07 17:51     ` Felipe Tonello
2013-06-07 18:37       ` Martin Jansa
2013-06-11  7:36         ` Khem Raj
2013-06-26 18:39           ` Felipe Tonello
2013-06-26 20:35             ` Saul Wold [this message]
2013-06-28 22:35             ` Khem Raj
2013-07-16 22:16 ` [PATCH v2] " eu
2013-07-16 22:54   ` Saul Wold
2013-07-16 23:09     ` Felipe Tonello

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=51CB50AD.2060008@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=eu@felipetonello.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.