From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [PATCH] common: add alsa-utils util-linux libpng for testing
Date: Fri, 15 Mar 2019 16:07:09 +0000 [thread overview]
Message-ID: <1552666029.2925.332.camel@codethink.co.uk> (raw)
In-Reply-To: <1552626432-7359-2-git-send-email-daniel.sangorrin@toshiba.co.jp>
On Fri, 2019-03-15 at 14:07 +0900, Daniel Sangorrin wrote:
> Patryk mentioned that they were using these packages for internal
> testing.
>
> Note: bonnie++ and imagemagick were also on the list but they are not
> supported by Deby at the moment.
ImageMagick has an appalling security record, so I don't think it would
make sense for CIP to try to support it.
Ben.
> Signed-off-by: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
> ---
> ?.../recipes-core/packagegroups/packagegroup-core-
> boot.bbappend?????????| 3 +++
> ?1 file changed, 3 insertions(+)
>
> diff --git a/poky/meta-cip-common/recipes-
> core/packagegroups/packagegroup-core-boot.bbappend b/poky/meta-cip-
> common/recipes-core/packagegroups/packagegroup-core-boot.bbappend
> index 4669429..d3637c3 100644
> --- a/poky/meta-cip-common/recipes-core/packagegroups/packagegroup-
> core-boot.bbappend
> +++ b/poky/meta-cip-common/recipes-core/packagegroups/packagegroup-
> core-boot.bbappend
> @@ -56,4 +56,7 @@ PKG_DEBUG = "\
> ? traceroute \
> ? iputils-ping \
> ? usbutils \
> + alsa-utils \
> + util-linux \
> + libpng \
> ?"
--
Ben Hutchings, Software Developer ? Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom
prev parent reply other threads:[~2019-03-15 16:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 5:07 [cip-dev] add a few tools to Deby CIP core for testing Daniel Sangorrin
2019-03-15 5:07 ` [cip-dev] [PATCH] common: add alsa-utils util-linux libpng " Daniel Sangorrin
2019-03-15 16:07 ` Ben Hutchings [this message]
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=1552666029.2925.332.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=cip-dev@lists.cip-project.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.