From: Saul Wold <sgw@linux.intel.com>
To: Paul Barker <paul@paulbarker.me.uk>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH RFC 1/3] opkg: Update to version 0.2.0
Date: Wed, 20 Nov 2013 10:33:33 -0800 [thread overview]
Message-ID: <528D007D.50306@linux.intel.com> (raw)
In-Reply-To: <1384965670-23435-2-git-send-email-paul@paulbarker.me.uk>
On 11/20/2013 08:41 AM, Paul Barker wrote:
> Signed-off-by: Paul Barker <paul@paulbarker.me.uk>
> ---
> meta/recipes-devtools/opkg/opkg_0.2.0.bb | 14 ++++++++++++++
> meta/recipes-devtools/opkg/opkg_svn.bb | 14 --------------
> 2 files changed, 14 insertions(+), 14 deletions(-)
> create mode 100644 meta/recipes-devtools/opkg/opkg_0.2.0.bb
> delete mode 100644 meta/recipes-devtools/opkg/opkg_svn.bb
>
> diff --git a/meta/recipes-devtools/opkg/opkg_0.2.0.bb b/meta/recipes-devtools/opkg/opkg_0.2.0.bb
> new file mode 100644
> index 0000000..7affbff
> --- /dev/null
> +++ b/meta/recipes-devtools/opkg/opkg_0.2.0.bb
> @@ -0,0 +1,14 @@
> +require opkg.inc
> +
> +SRC_URI = "https://opkg.googlecode.com/files/${BPN}-${PV}.tar.gz \
> + file://no-install-recommends.patch \
> + file://add-exclude.patch \
> + file://opkg-configure.service \
> +"
> +
> +S = "${WORKDIR}/${BPN}-${PV}"
> +
> +SRC_URI[md5sum] = "e8a6fd34fb2529191fe09dc14c934cc3"
> +SRC_URI[sha256sum] = "81b7055eb4c12c5e5652339305c9236cf357890717d4bea063963f3f434d966f"
> +
> +PR = "${INC_PR}.0"
Since we are creating new version, we can completely drop the PR here
and the INC_PR in the opkg.inc.
Sau!
> diff --git a/meta/recipes-devtools/opkg/opkg_svn.bb b/meta/recipes-devtools/opkg/opkg_svn.bb
> deleted file mode 100644
> index cd0485f..0000000
> --- a/meta/recipes-devtools/opkg/opkg_svn.bb
> +++ /dev/null
> @@ -1,14 +0,0 @@
> -require opkg.inc
> -
> -SRC_URI = "svn://opkg.googlecode.com/svn;module=trunk;protocol=http \
> - file://no-install-recommends.patch \
> - file://add-exclude.patch \
> - file://opkg-configure.service \
> -"
> -
> -S = "${WORKDIR}/trunk"
> -
> -SRCREV = "653"
> -PV = "0.1.8+svnr${SRCPV}"
> -
> -PR = "${INC_PR}.0"
>
next prev parent reply other threads:[~2013-11-20 18:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 16:41 [PATCH RFC 0/3] opkg upgrade Paul Barker
2013-11-20 16:41 ` [PATCH RFC 1/3] opkg: Update to version 0.2.0 Paul Barker
2013-11-20 18:33 ` Saul Wold [this message]
2013-11-20 16:41 ` [PATCH RFC 2/3] opkg: Add PACKAGECONFIG options Paul Barker
2013-11-20 16:41 ` [PATCH RFC 3/3] opkg: Don't use update-alternatives Paul Barker
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=528D007D.50306@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul@paulbarker.me.uk \
/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