**** BEGIN LOGGING AT Tue Jul 19 02:59:58 2016
Jul 19 08:40:02 <Jin^eLD> what's the best way to handle packages that provide the same files and thus conflict during build? is SSTATE_DUPWHITELIST the way to go?
Jul 19 08:40:56 <Jin^eLD> it's clear that both of those packages won't/can't be installed in the rootfs at the same time, but they should be buildable
Jul 19 09:03:03 <rburton> identical file?
Jul 19 09:03:23 <Jin^eLD> its firmware from different kernel versions
Jul 19 09:04:50 <Jin^eLD> so it might be different, but I could decide which package I actually install intherootfs
Jul 19 09:05:20 <Jin^eLD> however it seems OE won't let me to build those packages...
Jul 19 09:06:35 <rburton> well firmware is independent of kernel version, surely, so i'd delete it from all the kernels but the latest and have that put the firmware in a separate package
Jul 19 09:07:37 <Jin^eLD> mhm,I'd prefer to solve it in a generic facion, because the "latest kernel" pretty much depends on which target I am building for
Jul 19 09:07:53 <rburton> package the firmware independently?
Jul 19 09:07:57 <Jin^eLD> and we do have a tweaked kernel class that would actually allow building multiple kernels for the same target
Jul 19 09:07:59 <rburton> (thats what oe-core doe)
Jul 19 09:08:47 <Jin^eLD> uhm, this particular recipe does put the firmware in a separate ipk I think
Jul 19 09:09:08 <Jin^eLD> let me recheck
Jul 19 09:10:13 <Jin^eLD> yeah, it tries to I guess PACKAGES_DYNAMIC += "^kernel-${LINUX_VERSION}-firmware-.*"
Jul 19 09:10:57 <Jin^eLD> the actual error I get is: ERROR: The recipe linux-101 is trying to install files into a shared area when t
Jul 19 09:11:00 <Jin^eLD> hose files already exist.
Jul 19 09:11:48 <rburton> but they're all staging the same file
Jul 19 09:12:01 <rburton> what i meant is don't package the firmware via the kernel at all
Jul 19 09:12:16 <rburton> oe-core has linux-yocto which is just the kernel, and linux-firmware which is all the firmware
Jul 19 09:12:33 <Jin^eLD> hm
Jul 19 09:13:00 <Jin^eLD> and using firmware from a 4.x kernel on a 3.x kernel is OK/safe?
Jul 19 09:13:04 <Jin^eLD> I guess itis..?
Jul 19 09:14:38 <rburton> unless someone went and shipped a new piece of firmware that changes how the driver talks to it i guess so
Jul 19 09:15:22 <Jin^eLD> I think we don't even have the firmware installed
Jul 19 09:16:36 <Jin^eLD> I'll probably workaround by following your suggestion andwill simply not stage the firmare in the 3.x kernel recipes
Jul 19 09:18:17 <Jin^eLD> thanks
**** ENDING LOGGING AT Wed Jul 20 02:59:58 2016