From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Chang Rebecca Swee Fun <rebecca.swee.fun.chang@intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] bmap-tools: change SRC_URI to use tarball instead
Date: Fri, 9 Feb 2018 08:52:07 +0200 [thread overview]
Message-ID: <754a5028-97a1-79a3-fe48-232cea8d3a6d@linux.intel.com> (raw)
In-Reply-To: <1518150301-33101-1-git-send-email-rebecca.swee.fun.chang@intel.com>
On 02/09/2018 06:25 AM, Chang Rebecca Swee Fun wrote:
> -SRC_URI = "git://github.com/intel/bmap-tools.git"
> -SRCREV = "9dad724104df265442226972a1e310813f9ffcba"
> +SRC_URI = "https://github.com/intel/${BPN}/releases/download/v${PV}/${BPN}-${PV}.tgz"
When you switch the upstream source location like this, you need to
verify that upstream version check still works:
bitbake -c checkpkg bmap-tools
and inspect tmp/log/checkpkg.csv to see the outcome. If bitbake can no
longer determine the latest version, set UPSTREAM_CHECK_URI to the
webpage where all the tarballs are linked from (I think it would be
https://github.com/intel/${BPN}/releases/). There's plenty of recipes in
oe-core with similar adjustments, if you need further examples.
Alex
next prev parent reply other threads:[~2018-02-09 6:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 4:25 [PATCH 1/2] bmap-tools: change SRC_URI to use tarball instead Chang Rebecca Swee Fun
2018-02-09 4:25 ` [PATCH 2/2] maintainers.inc: change ownership for bmap-tools and wic-tools Chang Rebecca Swee Fun
2018-02-09 6:08 ` [PATCHv2] bmap-tools: change SRC_URI to use tarball instead rebecca.swee.fun.chang
2018-02-09 7:56 ` [PATCHv3] " rebecca.swee.fun.chang
2018-02-09 6:52 ` Alexander Kanavin [this message]
2018-02-09 7:14 ` [PATCH 1/2] " Chang, Rebecca Swee Fun
2018-02-09 7:44 ` Alexander Kanavin
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=754a5028-97a1-79a3-fe48-232cea8d3a6d@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rebecca.swee.fun.chang@intel.com \
/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.