[yocto] [meta-mono] Question about Q/A installed vs shipped failure

[Alex J Lennon]

Hi,

I'm looking at at the gtk-sharp recipe in meta-mono: 
http://git.yoctoproject.org/cgit/cgit.cgi/meta-mono/tree/recipes-mono/gtk-sharp/gtk-sharp_2.10.2.bb

This defines the contents of various gtk-sharp related packages making 
use of FILES_foo = and PACKAGES =

When I try to build against the Yocto head it fails a Q/A check with 
"ERROR: QA Issue: gtk-sharp: Files/directories were installed but not 
shipped"

Normally I would expect the extraneous files to be found in the image 
tree and add do_install_append() to rm the unneeded files from {$}D/foo/bar

However the behaviour of this recipe seems different.

For some reason the extraneous files are being found in the ../package 
tree. They are put there by the do_package() step, which is executed 
after my do_install_append().

I have tried adding a do_package_append() which I thought might help but 
bitbake won't accept this.

Can anybody advise:

(a) if files being in ./package indicates a problem with the recipe or 
if this is correct behaviour, and
(b) what is recommended practice to deal with this?

For now I am adding INSANE_SKIP_${PN} = "installed-vs-shipped" to the 
recipe but I'd rather not disable Q/A in this manner.

Thanks,

Alex


-- 
Dynamic Devices Ltd <http://www.dynamicdevices.co.uk/>

Alex J Lennon / Director
1 Queensway, Liverpool L22 4RA

mobile: +44 (0)7956 668178

Linkedin <http://www.linkedin.com/in/alexjlennon> Skype
<skype:alexjlennon?add>

This e-mail message may contain confidential or legally privileged
information and is intended only for the use of the intended
recipient(s). Any unauthorized disclosure, dissemination, distribution,
copying or the taking of any action in reliance on the information
herein is prohibited. E-mails are not secure and cannot be guaranteed to
be error free as they can be intercepted, amended, or contain viruses.
Anyone who communicates with us by e-mail is deemed to have accepted
these risks. Company Name is not responsible for errors or omissions in
this message and denies any responsibility for any damage arising from
the use of e-mail. Any opinion and other statement contained in this
message and any attachment are solely those of the author and do not
necessarily represent those of the company.