From: Martin Jansa <martin.jansa@gmail.com>
To: Cristian Iorga <cristian.iorga@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] libical: upgrade to 1.0.1
Date: Thu, 9 Jul 2015 16:32:48 +0200 [thread overview]
Message-ID: <20150709143248.GC2446@jama> (raw)
In-Reply-To: <ffb48ef3e2d7e9eb1e0adcff1226dd77b9b10553.1436452048.git.cristian.iorga@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1851 bytes --]
On Thu, Jul 09, 2015 at 05:28:11PM +0300, Cristian Iorga wrote:
> Bugfix release mainly.
> autotools build system removed, cmake is now used.
> perl is needed during the configure phase.
>
> Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>
> ---
> .../libical/{libical_1.0.0.bb => libical_1.0.1.bb} | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
> rename meta/recipes-support/libical/{libical_1.0.0.bb => libical_1.0.1.bb} (67%)
>
> diff --git a/meta/recipes-support/libical/libical_1.0.0.bb b/meta/recipes-support/libical/libical_1.0.1.bb
> similarity index 67%
> rename from meta/recipes-support/libical/libical_1.0.0.bb
> rename to meta/recipes-support/libical/libical_1.0.1.bb
> index be6b635..b50cf7e 100644
> --- a/meta/recipes-support/libical/libical_1.0.0.bb
> +++ b/meta/recipes-support/libical/libical_1.0.1.bb
> @@ -7,7 +7,10 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=d4fc58309d8ed46587ac63bb449d82f8 \
> SECTION = "libs"
>
> SRC_URI = "https://github.com/${BPN}/${BPN}/archive/v${PV}.tar.gz"
aren't github archives regenerated from time to time with different
checksums?
> -SRC_URI[md5sum] = "f4b8e33ae5efb2f025eb43ce69682a36"
> -SRC_URI[sha256sum] = "0072e83834092315772e6719b85fc8b11530b1ff53f4d108315fb38cddbce8c2"
> +SRC_URI[md5sum] = "af91db06b22559f863869c5a382ad08a"
> +SRC_URI[sha256sum] = "7d5f613454ec6c7d1bcfb441c919215be53292aa15cd1cb14249d1413d6c610c"
> +
> +inherit cmake perlnative
> +
> +FILES_${PN}-dev += "${libdir}/cmake"
>
> -inherit autotools
> --
> 2.1.4
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2015-07-09 14:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 14:28 [PATCH 0/2] BlueZ upgrades Cristian Iorga
2015-07-09 14:28 ` [PATCH 1/2] bluez5: upgrade to 5.32 Cristian Iorga
2015-07-09 14:28 ` [PATCH 2/2] libical: upgrade to 1.0.1 Cristian Iorga
2015-07-09 14:32 ` Martin Jansa [this message]
2015-07-09 15:09 ` Burton, Ross
2015-07-09 15:57 ` Iorga, Cristian
2015-07-09 16:04 ` Burton, Ross
2015-07-09 16:07 ` Iorga, Cristian
2015-07-09 16:09 ` Burton, Ross
2015-07-10 12:22 ` Martin Jansa
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=20150709143248.GC2446@jama \
--to=martin.jansa@gmail.com \
--cc=cristian.iorga@intel.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.