From: Tadek D <tdr...@ta...> - 2009-02-09 23:12:57
|
Chris, OK - I think I have a solution. It is slightly more complicated: 1) DEFAULT_PREFERENCE = "-1" inserted into xxx-1.0.1.bb causes that bitbake -c rebuild xxx will be using 1.0.0 and not 1.0.1. But if I bitbaked xxx 1.0.0 and 1.0.1 in the past I will end up with two ipk entries in tmp/deploy/glibc/glibc/ipk/armv5te/: xxx_1.0.0-r1_arm5te.ipk abd xxx_1.0.1-r1_arm5te.ipk 2) if I now bitbake -c gumstix-xxx-image, bitbake will use the newest xxx_1.0.1-r1_arm5te.ipk and the only way to produce rootfs corresponding to xxx 1.0.0 is to manually delete ipk corresponding to xxx 1.0.1 package from tmp/deploy directory Tad Oh... I wasn't reading close enough either :) Bitbake will always prefer the newest version of any given package unless you explicitly tell it not to. There are a couple of ways to do this. If you look in <gum-oe>/com.gumstix.collection/conf/machine/include/gumstix.inc you'll see a number of PREFERRED_VERSION_xxx lines -- you could add a line like that for your package specifying the 1.0.0 version. Another way is to add the line DEFAULT_PREFERENCE = "-1" to the 1.0.1 recipe which will tell bitbake basically the same thing. Chris -- View this message in context: http://www.nabble.com/rebuilding-root-file-system-image-tp21862475p21924300.html Sent from the Gumstix mailing list archive at Nabble.com. |