From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] hal-0.5.12 requires blkid >= 1.43
Date: Tue, 21 Jul 2009 12:31:59 +0200 [thread overview]
Message-ID: <h445ev$pe3$1@ger.gmane.org> (raw)
In-Reply-To: <4A657D58.4070404@atmel.com>
On 21-07-09 10:33, Ulf Samuelsson wrote:
> diff -urN a/configure b/configure
> --- a/configure 2009-07-21 10:02:37.000000000 +0200
> +++ b/configure 2009-07-21 10:06:27.000000000 +0200
> @@ -2791,7 +2791,7 @@
>
> glib_module="glib-2.0>= 2.10.0 gobject-2.0> 2.10.0 dbus-glib-1>= 0.61"
> dbus_module="dbus-1>= 0.61"
> -blkid_module="blkid>= 1.43"
> +blkid_module="blkid>= 1.41"
> polkit_module="polkit>= 0.5"
>
> # libtool versioning - this applies to libhal and libhal-storage
> diff -urN a/configure.in b/configure.in
> --- a/configure.in 2009-05-10 21:43:52.000000000 +0200
> +++ b/configure.in 2009-07-21 10:06:51.000000000 +0200
> @@ -13,7 +13,7 @@
>
> glib_module="glib-2.0>= 2.10.0 gobject-2.0> 2.10.0 dbus-glib-1>= 0.61"
> dbus_module="dbus-1>= 0.61"
> -blkid_module="blkid>= 1.43"
> +blkid_module="blkid>= 1.41"
> polkit_module="polkit>= 0.5"
>
> # libtool versioning - this applies to libhal and libhal-storage
>
>
> Comments?
configure gets generated from configure.in, so you only have to patch
one file. And please use git-format-patch to make a single patch next time.
Anyway, I solved it in a different way.
regards,
Koen
next prev parent reply other threads:[~2009-07-21 10:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 8:33 [RFC] hal-0.5.12 requires blkid >= 1.43 Ulf Samuelsson
2009-07-21 10:31 ` Koen Kooi [this message]
2009-07-21 10:38 ` Florian Boor
2009-07-21 11:46 ` Koen Kooi
2009-07-21 12:13 ` Koen Kooi
2009-07-21 10:44 ` Phil Blundell
2009-07-21 16:39 ` Ulf Samuelsson
2009-07-21 18:00 ` Phil Blundell
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='h445ev$pe3$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.