From: "Maxin B. John" <maxin.john@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/4] freetype: fix upstream check
Date: Thu, 19 May 2016 16:43:07 +0300 [thread overview]
Message-ID: <1463665389-18822-2-git-send-email-maxin.john@intel.com> (raw)
In-Reply-To: <1463665389-18822-1-git-send-email-maxin.john@intel.com>
Provide UPSTREAM_CHECK_URI and UPSTREAM_CHECK_REGEX for proper
upstream check.
Signed-off-by: Maxin B. John <maxin.john@intel.com>
---
meta/recipes-graphics/freetype/freetype_2.6.3.bb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/recipes-graphics/freetype/freetype_2.6.3.bb b/meta/recipes-graphics/freetype/freetype_2.6.3.bb
index 3ed9070..bcd5044 100644
--- a/meta/recipes-graphics/freetype/freetype_2.6.3.bb
+++ b/meta/recipes-graphics/freetype/freetype_2.6.3.bb
@@ -15,6 +15,9 @@ LIC_FILES_CHKSUM = "file://docs/LICENSE.TXT;md5=4af6221506f202774ef74f64932878a1
SRC_URI = "${SOURCEFORGE_MIRROR}/freetype/freetype-${PV}.tar.bz2 \
file://use-right-libtool.patch"
+UPSTREAM_CHECK_URI = "http://sourceforge.net/projects/freetype/files/freetype2/"
+UPSTREAM_CHECK_REGEX = "(?P<pver>\d+(\.\d+)+)"
+
SRC_URI[md5sum] = "0037b25a8c090bc8a1218e867b32beb1"
SRC_URI[sha256sum] = "371e707aa522acf5b15ce93f11183c725b8ed1ee8546d7b3af549863045863a2"
--
2.4.0
next prev parent reply other threads:[~2016-05-19 13:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 13:43 [PATCH 1/4] package_regex.inc: remove deprecated file Maxin B. John
2016-05-19 13:43 ` Maxin B. John [this message]
2016-05-19 13:43 ` [PATCH 3/4] libgudev: fix upstream check Maxin B. John
2016-05-19 13:43 ` [PATCH 4/4] ghostscript: " Maxin B. John
2016-05-19 14:04 ` Burton, Ross
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=1463665389-18822-2-git-send-email-maxin.john@intel.com \
--to=maxin.john@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.