[oe] reverting some csets that kill package upgrade paths
k.kooi at student.utwente.nl
Fri Apr 24 19:32:57 CEST 2009
Recently the e17 people made a change to how libtool names their
libraries by poking in some magic string (ver-pre-svn-00) into SONAME.
This has some implications for OE, namely that you get the old *and* new
lib in your rootfs. There was one bug that killed everything at runtime:
So after that cset you'd get a completely working rootfs again with e17
Today a few csets have been pushed that break things horribly:
Let's take a look at the generated packages:
So suddenly the library packages (or plugin packages, but no difference
in this case) have a new name, but don't set RPROVIDES or RREPLACES to
the old packages containing *the same files*. This means that 'opkg
install <foo>' or 'opkg upgrade' doesn't work anymore. It will abort
saying to package <foo> wants to overwrite files belonging to <bar>.
Depending on the way you build your images in OE, your build will break.
My position is that breaking upgrade patch unacceptable without prior
notice and that the above 3 csets get reverted ASAP.
The changes in question are not intrinsically bad, and the autosplitting
is way better than manually poking at FILES_foo, but right now they
break way too much at runtime.
More information about the Openembedded-devel