> On Jan 11, 2016, at 3:13 AM, Chris Trobridge <[email protected]> > wrote: > > Hi, > > I have been looking into producing a 'python3-dbus' recipe, based on the > python-dbus recipe. > > This recipe outputs a couple of files that are version independent but end up > overlapping and causing the build to fail: > /usr/lib/pkgconfig/dbus-python.pc > /usr/include/dbus-1.0/dbus/dbus-python.h
you can let one provide it and then delete it from other recipe but it means now you created a dependency also second option is to install the files after renaming. e.g. dbus-python3.pc and dbus-python3.h the may be you can use alternatives mechanism to symlink python3 versions to provide python2 versions as well only if python2 is not installed. > > These files are currently marked as python-version independent - the header > file has #ifdefs for python3. > > The immediate 'fix' was to follow the advice in the error text to add the > file paths to SSTATE_DUPWHITELIST. > > SSTATE_DUPWHITELIST is not mentioned much elsewhere and does not seem like a > scalable solution. Is there a preferred method to resolve the situation > where two recipes install the same files? > > Thanks, > Chris > > -- > _______________________________________________ > Openembedded-core mailing list > [email protected] > <mailto:[email protected]> > http://lists.openembedded.org/mailman/listinfo/openembedded-core > <http://lists.openembedded.org/mailman/listinfo/openembedded-core>
signature.asc
Description: Message signed with OpenPGP using GPGMail
-- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
