Op 25 mei 2012, om 12:02 heeft Robert Yang het volgende geschreven: > There is a bug if we: > 1) bitbake core-image-sato-sdk MACHINE=qemux86 > 2) bitbake core-image-sato with MACHINE=crownbay > > Then several pkgs in deploy/ipk/i586 would be installed to crownbay's > image even if there is one in deploy/ipk/core2 and we have set the > core2's priority higher than i586, when the version in deploy/ipk/i586 is > higher. This doesn't work for us, for example, what the crownbay need is > xserver-xorg-1.9.3, but it installs xserver-xorg-1.11.2. > > This is caused by opkg's selecting mechanism, if there are more than one > candidates which have the same pkg name in the candidate list, for > example, the same pkg with different versions, then it will use the last > one which is the highest version in the list, this doesn't work for us, > it should respect to the arch priorities in such a case.
This is a serious break with the current opkg behaviour and I don't think it's an improvement. Needing different versions for non machine specific packages indicates a more serious bug elsewhere. _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
