From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 2/3] media-ctl: remove package
Date: Wed, 7 Oct 2015 12:57:00 +0100 [thread overview]
Message-ID: <5615088C.60004@mind.be> (raw)
In-Reply-To: <1444165338-19896-2-git-send-email-ps.report@gmx.net>
On 06-10-15 22:02, Peter Seiderer wrote:
> Package media-ctl is out-dated, source (and developement) have been moved
> to v4l-utils since June 2014. Up-to-date version is available in
> the libv4l package (BR2_PACKAGE_LIBV4L/BR2_PACKAGE_LIBV4L_UTILS).
>
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> ---
> Config.in.legacy | 7 +
> package/Config.in | 1 -
> ...ers-for-compatibility-with-old-toolchains.patch | 303 ---------------------
> package/media-ctl/Config.in | 9 -
> package/media-ctl/media-ctl.mk | 17 --
> 5 files changed, 7 insertions(+), 330 deletions(-)
> delete mode 100644 package/media-ctl/0001-add-kernel-headers-for-compatibility-with-old-toolchains.patch
> delete mode 100644 package/media-ctl/Config.in
> delete mode 100644 package/media-ctl/media-ctl.mk
>
> diff --git a/Config.in.legacy b/Config.in.legacy
> index 3c7fe36..4b7e201 100644
> --- a/Config.in.legacy
> +++ b/Config.in.legacy
> @@ -107,6 +107,13 @@ endif
> ###############################################################################
> comment "Legacy options removed in 2015.11"
>
> +config BR2_PACKAGE_MEDIA_CTL
> + bool "media-ctl package has been removed"
> + help
> + media-ctl source and developement have been moved to
> + v4l-utils since June 2014. For an up-to-date media-ctl
> + version select BR2_PACKAGE_LIBV4L and BR2_PACKAGE_LIBV4L_UTILS.
These two options should be selected automatically. See e.g.
BR2_PACKAGE_DIRECTFB_EXAMPLES_ANDI
You should also select BR2_LEGACY.
> +
> config BR2_PACKAGE_SCHIFRA
> bool "schifra package has been removed"
Oops, here BR2_LEGACY is not selected... And in a couple of other places as well...
Regards,
Arnout
> help
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-10-07 11:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 21:02 [Buildroot] [PATCH v1 1/3] libv4l: update v4l-utils help text (add more listed tools) Peter Seiderer
2015-10-06 21:02 ` [Buildroot] [PATCH v1 2/3] media-ctl: remove package Peter Seiderer
2015-10-07 11:57 ` Arnout Vandecappelle [this message]
2015-10-07 15:44 ` Peter Seiderer
2015-10-06 21:02 ` [Buildroot] [PATCH v1 3/3] libv4l: bump version to 1.8.0 Peter Seiderer
2015-10-07 7:35 ` [Buildroot] [PATCH v1 1/3] libv4l: update v4l-utils help text (add more listed tools) Thomas Petazzoni
2015-10-07 15:50 ` Peter Seiderer
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=5615088C.60004@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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