From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] setxkbmap: upgrade to 1.3.0
Date: Wed, 19 Nov 2014 15:28:57 +0100 [thread overview]
Message-ID: <20141119142857.GD3315@jama> (raw)
In-Reply-To: <1415699604-2155-1-git-send-email-lixin.fnst@cn.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 2517 bytes --]
On Tue, Nov 11, 2014 at 05:53:24PM +0800, Li xin wrote:
> Signed-off-by: Li Xin <lixin.fnst@cn.fujitsu.com>
> ---
> meta-oe/recipes-graphics/xorg-app/setxkbmap_1.2.0.bb | 8 --------
> meta-oe/recipes-graphics/xorg-app/setxkbmap_1.3.0.bb | 19 +++++++++++++++++++
> 2 files changed, 19 insertions(+), 8 deletions(-)
> delete mode 100644 meta-oe/recipes-graphics/xorg-app/setxkbmap_1.2.0.bb
> create mode 100644 meta-oe/recipes-graphics/xorg-app/setxkbmap_1.3.0.bb
>
> diff --git a/meta-oe/recipes-graphics/xorg-app/setxkbmap_1.2.0.bb b/meta-oe/recipes-graphics/xorg-app/setxkbmap_1.2.0.bb
> deleted file mode 100644
> index 127b0f6..0000000
> --- a/meta-oe/recipes-graphics/xorg-app/setxkbmap_1.2.0.bb
> +++ /dev/null
> @@ -1,8 +0,0 @@
> -require recipes-graphics/xorg-app/xorg-app-common.inc
> -LIC_FILES_CHKSUM = "file://COPYING;md5=5feafdbe6dfe9e2bd32325be0cfc86f8"
> -DEPENDS += " libxkbfile"
> -PE = "1"
> -PR = "r6"
> -
> -SRC_URI[md5sum] = "2f6df89201eb9a2cbfb905d6b82a191e"
> -SRC_URI[sha256sum] = "999591bf1ba8ca2a7d480b2c01702396e6c349d499fb583c0de136ec00dbae39"
> diff --git a/meta-oe/recipes-graphics/xorg-app/setxkbmap_1.3.0.bb b/meta-oe/recipes-graphics/xorg-app/setxkbmap_1.3.0.bb
> new file mode 100644
> index 0000000..2b9a8c4
> --- /dev/null
> +++ b/meta-oe/recipes-graphics/xorg-app/setxkbmap_1.3.0.bb
> @@ -0,0 +1,19 @@
> +require recipes-graphics/xorg-app/xorg-app-common.inc
> +
> +SUMMARY = "A program to compile XKB keyboard description"
> +
> +DESCRIPTION = "The xkbcomp keymap compiler converts a description of an \
> +XKB keymap into one of several output formats. The most common use for \
> +xkbcomp is to create a compiled keymap file (.xkm extension) which can \
> +be read directly by XKB-capable X servers or utilities."
> +
> +LIC_FILES_CHKSUM = "file://COPYING;md5=5feafdbe6dfe9e2bd32325be0cfc86f8"
> +
> +PR = "${INC_PR}.0"
You cannot drop PE, but you should drop PR.
I'll fix when cherry-picking to master-next.
> +
> +DEPENDS += "libxkbfile"
> +
> +BBCLASSEXTEND = "native"
> +
> +SRC_URI[md5sum] = "1001771344608e120e943a396317c33a"
> +SRC_URI[sha256sum] = "3d305c9d1f38224169b2e501ef0665cc3ab52d4dbc2b9a60c9dbb047f77ddec6"
> --
> 1.8.4.2
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2014-11-19 14:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 9:53 [PATCH] setxkbmap: upgrade to 1.3.0 Li xin
2014-11-19 14:28 ` Martin Jansa [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=20141119142857.GD3315@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@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