On Wed, Mar 23, 2011 at 11:47:55AM +0100, Stefan Schmidt wrote: > Hello. > > On Fri, 2011-03-18 at 15:00, Martin Jansa wrote: > > * libnl1/libnl2 still conflicts even when using separate includedir so > > it will be easier for distro maintainers to use only libnl1 or libnl2 > > by PREFERRED_VERSION > > For distros that want to support network-manager that still means that > both versions are being build and may clash as we have seen before.
How do you build 2 versions of same package? Whole point of this patch series is to force distromaintainers to use only libnl_2.0.0 or libnl_1.1.0 based on PREFERRED_VERSION_libnl and this way keep them away from shooting own foot by accident. > Just a remark. Personally I would like to go this route and maybe get > rid of libnl1 at all. Yes this is step in direction to get rid of libnl1 :). I'm using libnl_2.0.0 from oe-core in meta-shr, so this change is making diff between recipes in oe.dev and meta-shr smaller. Regards, -- Martin 'JaMa' Jansa jabber: [email protected]
pgpcTJ5J2pGDr.pgp
Description: PGP signature
_______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
