From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] Upgrade guile from 1.8.6 to 1.8.7.
Date: Fri, 20 Nov 2009 09:22:04 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0911200916270.11844@localhost> (raw)
In-Reply-To: <4B068A46.8090701@balister.org>
On Fri, 20 Nov 2009, Philip Balister wrote:
> 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.
ok, there's some curious stuff going on there. first, while the
newest curl .bb file is version 7.19.7, there is no equivalent
curl-native .bb file, even though earlier version have them. is there
a reason for that?
also, it's only that latest .bb file -- curl_7.19.7.bb -- that has
the tarball checksums. if there *was* a corresponding -native .bb
file, would it *also* need those identical checksums? i would like to
think not since that would be redundant. a grep of recipes shows only
two recipes that appear to be taking advantage of this feature --
busybox and curl.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
next prev parent reply other threads:[~2009-11-20 14:23 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
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 [this message]
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=alpine.LFD.2.00.0911200916270.11844@localhost \
--to=rpjday@crashcourse.ca \
--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 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.