From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] mokosuite2: Add `libfakekey` and `vala-native` to DEPENDS.
Date: Wed, 6 Oct 2010 16:25:38 +0200 [thread overview]
Message-ID: <20101006142538.GJ3264@jama> (raw)
In-Reply-To: <1286374774.3792.12.camel@mattotaupa>
On Wed, Oct 06, 2010 at 04:19:34PM +0200, Paul Menzel wrote:
>
> During the latest bumps of `SRCREV` I guess it was forgotten to add some dependencies.
>
> `libfakekey` is needed for a successful configure and without `vala-native` `valac` is not found on a clean and minimal build system.
>
> Signed-off-by: Paul Menzel <paulepanter@users.sourceforge.net>
Acked-by: Martin Jansa <Martin.Jansa@gmail.com>
IMHO no need to bump PR as it won't change resulting packages, but won't
harm as it builds quickly.
Thanks for spotting it.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
next prev parent reply other threads:[~2010-10-06 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 14:19 [PATCH] mokosuite2: Add `libfakekey` and `vala-native` to DEPENDS Paul Menzel
2010-10-06 14:25 ` Martin Jansa [this message]
2010-10-06 14:56 ` [PATCH v2] mokosuite2: Add `libfakekey` and `vala-native` to `DEPENDS` Paul Menzel
2010-10-06 15:11 ` Martin Jansa
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=20101006142538.GJ3264@jama \
--to=martin.jansa@gmail.com \
--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