Op 10 apr. 2012, om 11:06 heeft Richard Purdie het volgende geschreven: > On Tue, 2012-04-10 at 10:38 +0200, Martin Jansa wrote: >> On Fri, Apr 06, 2012 at 12:17:38AM +0000, g...@git.openembedded.org wrote: >>> Module: openembedded-core.git >>> Branch: master >>> Commit: e4d2ee00419f675ba8b7fb5d75256762253d8b32 >>> URL: >>> http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=e4d2ee00419f675ba8b7fb5d75256762253d8b32 >>> >>> Author: Andrei Gherzan <and...@gherzan.ro> >>> Date: Fri Mar 23 17:56:29 2012 +0200 >>> >>> gdbm: Activate -enable-libgdbm-compat and add symlinks to headers in >>> include/gdbm >>> >>> ndbm.h is needed by python for dbm module. This is why >>> -enable-libgdbm-compat was added >>> to configure. >>> The second change is because python is looking for the gdbm headers in >>> include/gdbm. >>> The easiest way to solve this issue is to add symlinks in include/gdbm. >>> >>> [YOCTO #1937] >>> >>> Signed-off-by: Andrei Gherzan <and...@gherzan.ro> >> >> This breaks every package in feed which depends on old package name >> libgdbm4 (>= 1.10) >> >> Because now there are 2 .so files in ${PN} and no LEAD_SONAME defined. >> >> Are you going to >> >> 1) send PR bumps to all packages which depends on libgdbm4 >> (e.g. apr-util python pulseaudio perl gst-plugins-good and probably more) >> 2) define LEAD_SONAME and bump PR in gdbm recipe >> 3) move -compat libs to ${PN}-compat or some other package name, so that >> old libgdbm4 still exists (and maybe + 1) because some people could >> build those with gdbm as dependency now) > > I like the idea of putting the compat libs into a separate package...
me too regards, Koen _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core