**** BEGIN LOGGING AT Thu Nov 19 02:59:58 2015 Nov 19 08:07:20 good morning Nov 19 11:37:41 why is it "insane" to rdepends a -dev package? Nov 19 11:43:38 if there's a genuine reason then you can whitelist the warning Nov 19 11:43:52 but generally you don't want a normal package to depend on a devel package Nov 19 12:01:48 JaMa: did you receive negative feedback on http://article.gmane.org/gmane.comp.handhelds.openembedded/71808 ? Nov 19 12:09:00 oh I see it's still in master-next Nov 19 12:34:17 funman: meta-networking has 2nd maintainer Joe, so I haven't merged this one Nov 19 13:09:27 funman: your pull-request looks strange, will you send the individual changes as well? Nov 19 13:09:44 funman: I got only one e-mail which looks like cover letter, but with all changes squashed in it Nov 19 13:10:44 JaMa: yes, I used git pull-request -p to include the changes since they were quite small Nov 19 13:10:54 I will send individual patches if you prefer Nov 19 13:11:23 I just wanted to put my contrib branch to use :( Nov 19 13:12:25 JaMa: I thought it might be easier for you to pull directly rather than applying the patches one by one Nov 19 13:15:43 here you go Nov 19 13:53:05 funman: both are OK for me, because as you say they are simple, but either send them as one patch or as separate patches, this pull request was kind of hybrid between these 2 Nov 19 13:53:21 funman: you can also use scripts/create-pull-request and send-pull-request scripts in oe-core Nov 19 13:55:44 nice, will check these scripts Nov 19 13:55:45 funman: looks good, just not sure about the "notify" one, did you verify it doesn't autodetect any deps now when you remove gtk+? Nov 19 13:58:42 do you mean, does it detect any *missing* deps? Nov 19 13:59:56 I had no warnings when re-building vlc Nov 19 14:00:26 and I can't think of gtk dependencies that vlc would depend on directly besides gstreamer, notify and rsvg Nov 19 14:02:43 I plan to go manually through every vlc dependencies by reading its configure.ac if this patch set goes in Nov 19 14:03:27 if you still have a doubt about notify you can just leave it out and I will put it again in the next patch set (which hopefully will be sent correctly on the first try ;) Nov 19 14:08:41 it can warn only about deps you've built before vlc Nov 19 14:08:41 if you build gtk+ and libnotify Nov 19 14:09:05 and then rebuild vlc (cleansstate), and it still doesn't show any warnings then it should be fine Nov 19 14:09:32 i only relied on the recipe being updated, I didn't do manual clean before rebuilding vlc Nov 19 14:09:54 I just remember couple new warnings caused by last version of this change, there were many new PACKAGECONFIGs since then, so it could be fine now Nov 19 14:10:14 yeah I think you took care of it Nov 19 14:11:05 bitbake -c cleansstate vlc ; bitbake vlc ? Nov 19 14:17:11 LaForge ‏@LaF0rge 11m11 minutes ago Nov 19 14:17:11 @balister I would hope there is a simple bitbake command where i can ask 'what provides foo' to resolve which recipe generates a package? Nov 19 14:17:19 anyone have a better answer than grep? Nov 19 14:20:34 JaMa: no warnings Nov 19 14:42:40 funman: good, thanks for verification Nov 19 17:35:02 Crofton|work: what about 2 logos that fit together like puzzle pieces? Nov 19 17:52:30 hi, does someone know how to only include the -native targets even if the cross / native / nativesdk is defined in a single .bb? Nov 19 17:54:13 jeroen_: what do you mean by "only include"? Nov 19 17:55:51 bluelightning: hacking around, what I would like to do is include all *.bb from oe-core and drop all the recipes for the target (and keep the -native onces) Nov 19 17:57:55 bluelightning: or perhaps it is clearer put as, drop the PACKAGES which are intended for the MACHINE, but keep the -native PACKAGES... Nov 19 17:58:42 since a single bb can "define"? them all I cannot simply drop bb from the layer.conf Nov 19 17:59:53 I'm not sure you can really do that Nov 19 18:00:10 can you shed some light on what the ultimate goal is? Nov 19 18:02:10 bluelightning: the ultimate goal is building a oe "Software" layer against a binary deb feed, with the help of the native / cross tools from oe-core (but not the once for the target since they come from the deb feed) Nov 19 18:06:32 well, good luck with that ;) Nov 19 18:07:33 you'd probably try to do something like this by inheriting a class at the global scope and then using overrides or anonymous python to make changes for just the native variants of recipes Nov 19 18:08:21 bluelightning: thanks :) well at least it is fun... Nov 19 18:17:41 funman: thanks for the work on vlc! Nov 19 18:20:45 a bit of topic trying to setup an external linaro compiler warns about "QA Issue: external-linaro-toolchain: Files/directories were installed but not shipped in any package", is that a known feature? Nov 19 18:22:42 hmm, you'd need to ask the maintainers of that layer, but that sounds like a bug in their toolchain layer Nov 19 18:23:31 otavio: got a little busy, and the boards are still on back-order Nov 19 18:23:56 nerdboy: uh!? Nov 19 18:24:00 they sent some cables or something (not very useful yet) Nov 19 18:24:22 we're still on the olinuxino nano/blah path... Nov 19 18:24:35 just taking longer than i thought Nov 19 18:25:16 nerdboy: oh ok Nov 19 18:25:22 should get at least 2 of the ones on the "unsupported" list Nov 19 20:10:30 moto-timo: no problem.. next i'll look at which patches i can merge in vlc 3.0 Nov 19 20:21:31 funman: I have three that I put in a PR on github... before I read the ignore disclaimer Nov 19 20:22:03 funman: also, feel free to start a -contrib/vlc-next branch staging changes for vlc 3.0 Nov 19 20:22:15 funman: we can collaborate without affecting anybody else **** ENDING LOGGING AT Fri Nov 20 02:59:58 2015