From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Maxin B. John" <maxin.john@enea.com>
Cc: yocto@yoctoproject.org, scott.a.garman@intel.com,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] latencytop: add sudo as runtime dependency
Date: Fri, 04 Jan 2013 14:27:42 +0000 [thread overview]
Message-ID: <1357309662.28649.127.camel@ted> (raw)
In-Reply-To: <1357299055-56828-1-git-send-email-maxin.john@enea.com>
On Fri, 2013-01-04 at 12:30 +0100, Maxin B. John wrote:
> From: "Maxin B. John" <maxin.john@enea.com>
>
> Latencytop needs superuser privileges. The latencytop plugin in
> eclipse invokes it as 'sudo latencytop'. So, it will be good to
> include sudo as a runtime dependency.
>
> Signed-off-by: Maxin B. John <maxin.john@enea.com>
> ---
> meta/recipes-kernel/latencytop/latencytop_0.5.bb | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/meta/recipes-kernel/latencytop/latencytop_0.5.bb b/meta/recipes-kernel/latencytop/latencytop_0.5.bb
> index 3e35bf9..a148a47 100644
> --- a/meta/recipes-kernel/latencytop/latencytop_0.5.bb
> +++ b/meta/recipes-kernel/latencytop/latencytop_0.5.bb
> @@ -7,6 +7,9 @@ LIC_FILES_CHKSUM = "file://latencytop.c;endline=23;md5=ee9ea9b1415356e5734adad4a
>
> DEPENDS = "virtual/libintl ncurses glib-2.0 ${@base_contains('DISTRO_FEATURES', 'x11', 'gtk+', '', d)}"
>
> +# latencytop and it's eclipse support need sudo
> +RDEPENDS_${PN} = "sudo"
> +
> PR = "r3"
Shouldn't the eclipse support RDEPEND on sudo, not latencytop? There are
several ways you could run latencytop without sudo...
Following this logic, we'd add an RDEPENDS on sudo for every app that
could possibly need root privs.
Cheers,
Richard
next prev parent reply other threads:[~2013-01-04 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 11:30 [PATCH] latencytop: add sudo as runtime dependency Maxin B. John
2013-01-04 14:27 ` Richard Purdie [this message]
2013-01-04 15:41 ` Maxin B. John
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=1357309662.28649.127.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=maxin.john@enea.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=scott.a.garman@intel.com \
--cc=yocto@yoctoproject.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.