From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] Upgrade guile from 1.8.6 to 1.8.7.
Date: Fri, 20 Nov 2009 07:23:34 -0500 [thread overview]
Message-ID: <4B068A46.8090701@balister.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0911200514430.18485@localhost>
I applied this. A couple of comments for the future:
1) Make the commit message "guile: Upgrade from 1.8.6 to 1.8.7" for
consistency.
2) You can include the checksums in the recipe now. See:
http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/curl/curl_7.19.7.bb
look in the curl-common.inc file for the "tarball" naming.
Thanks,
Philip
On 11/20/2009 05:16 AM, Robert P. J. Day wrote:
>
> Signed-off-by: Robert P. J. Day<rpjday@crashcourse.ca>
>
> ---
>
> bitbake tested on x86_64.
>
> diff --git a/conf/checksums.ini b/conf/checksums.ini
> index b2bc05b..5529b73 100644
> --- a/conf/checksums.ini
> +++ b/conf/checksums.ini
> @@ -11426,6 +11426,10 @@ sha256=e2f63d2d445ffeb072638eab885b1a629e372d1db711c8afb26a62bc56096289
> md5=9e23d3dbea0e89bab8a9acc6880150de
> sha256=69a2f9491480ff756d1cc4c8ea2bdc13d40ea8ddc8f93f26957bade8219a1d86
>
> +[http://ftp.gnu.org/pub/gnu/guile/guile-1.8.7.tar.gz]
> +md5=991b5b3efcbbc3f7507d05bc42f80a5e
> +sha256=bfee6339d91955a637e7f541d96f5b1d53271b42bb4a37b8867d186a6c66f0b3
> +
> [http://gupnp.org/sources/gupnp/gupnp-0.12.2.tar.gz]
> md5=5350f5f28fb3742779702a496ab75d72
> sha256=9e4edb3ca6d11e397d9f98537fa8954851dc044d13ecafd4f4547117cefbdd28
> diff --git a/recipes/guile/guile-native_1.8.7.bb b/recipes/guile/guile-native_1.8.7.bb
> new file mode 100644
> index 0000000..2f87c48
> --- /dev/null
> +++ b/recipes/guile/guile-native_1.8.7.bb
> @@ -0,0 +1,5 @@
> +require guile-native.inc
> +SRC_URI = "http://ftp.gnu.org/pub/gnu/guile/guile-${PV}.tar.gz \
> + file://configure-fix.patch;patch=1 \
> + file://cpp-linemarkers.patch;patch=1 \
> + "
> diff --git a/recipes/guile/guile_1.8.7.bb b/recipes/guile/guile_1.8.7.bb
> new file mode 100644
> index 0000000..6889f33
> --- /dev/null
> +++ b/recipes/guile/guile_1.8.7.bb
> @@ -0,0 +1,6 @@
> +require guile.inc
> +
> +SRC_URI = "http://ftp.gnu.org/pub/gnu/guile/guile-${PV}.tar.gz \
> + file://configure-fix.patch;patch=1 \
> + "
> +
>
> ========================================================================
> Robert P. J. Day Waterloo, Ontario, CANADA
>
> Linux Consulting, Training and Kernel Pedantry.
>
> Web page: http://crashcourse.ca
> Twitter: http://twitter.com/rpjday
> ========================================================================
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
next prev parent reply other threads:[~2009-11-20 12:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 10:16 [PATCH] Upgrade guile from 1.8.6 to 1.8.7 Robert P. J. Day
2009-11-20 12:23 ` Philip Balister [this message]
2009-11-20 12:28 ` Robert P. J. Day
2009-11-20 12:41 ` Philip Balister
2009-11-20 13:16 ` Robert P. J. Day
2009-11-20 12:30 ` Koen Kooi
2009-11-20 14:22 ` Robert P. J. Day
2009-11-23 11:51 ` Marc Olzheim
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=4B068A46.8090701@balister.org \
--to=philip@balister.org \
--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