From: Martin Jansa <martin.jansa@gmail.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: openembedded-commits@lists.openembedded.org
Subject: Re: [oe-commits] Ross Burton : Add gtk-doc-stub
Date: Mon, 23 Jul 2012 11:18:09 +0200 [thread overview]
Message-ID: <20120723091809.GC3271@jama.jama.net> (raw)
In-Reply-To: <CAJTo0LYK43FiO-iJ3wQf3Dsid14ckSkW9cAGhKtBUV8sDACd2Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
On Mon, Jul 23, 2012 at 10:06:54AM +0100, Burton, Ross wrote:
> On 23 July 2012 09:15, Martin Jansa <martin.jansa@gmail.com> wrote:
> > This has couple of unpackaged files:
> >
> > NOTE: package gtk-doc-stub-0.0+git1+3dfd0a09de696ec8c544762747f8a0f77153622e-r0: task do_package: Started
> > WARNING: QA Issue: gtk-doc-stub: Files/directories were installed but not shipped
> > /usr/share/gtk-doc-devel
> > /usr/share/gobject-introspection-1.0
> > /usr/share/gtk-doc-devel/gtk-doc.make
> > /usr/share/gobject-introspection-1.0/Makefile.introspection
> > NOTE: package gtk-doc-stub-0.0+git1+3dfd0a09de696ec8c544762747f8a0f77153622e-r0: task do_package: Succeeded
>
> Good point, I never tested the non-native package because it's
> generally going to be used in a native context.
For some reason non-native gtk-doc-stub is pulled to image dependency
tree for me after last oe-core changes. I'll check dep graph.. if that's
not expected.
Cheers,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2012-07-23 9:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120722104320.C057610218@opal>
2012-07-23 8:15 ` [oe-commits] Ross Burton : Add gtk-doc-stub Martin Jansa
2012-07-23 9:06 ` Burton, Ross
2012-07-23 9:18 ` Martin Jansa [this message]
2012-07-23 9:24 ` Burton, Ross
2012-07-23 9:40 ` Burton, Ross
2012-07-23 11:30 ` Martin Jansa
2012-07-23 12:19 ` Burton, Ross
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=20120723091809.GC3271@jama.jama.net \
--to=martin.jansa@gmail.com \
--cc=openembedded-commits@lists.openembedded.org \
--cc=openembedded-core@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