[oe] reverting some csets that kill package upgrade paths
marcin at juszkiewicz.com.pl
Sat Apr 25 23:18:17 CEST 2009
Dnia piątek, 24 kwietnia 2009 o 19:32:57 Koen Kooi napisał(a):
> 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 stuff.
First I want to say that I am total ignorant when it comes to E17. I
have it installed on Beagleboard just because it is part of
'beagleboard-demo-image' which I installed. As it I did not built it
during last 2 years on any of my machines. Thats some kind of
> Today a few csets have been pushed that break things horribly:
I see edje RRECOMMENDS adapted to other changes here (not counting PV
This one looks quite sane.
s/libevas/evas - but should not debian.bbclass take care of that?
> Let's take a look at the generated packages:
So why not change call to populate_packages_prepend() to make old names
again? That way we will get autosplit (which is good) and old names
(which will keep some kind of upgrade path).
> 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.
Provide a patch which will add such ones? We have many developers in OE
- some of them use OE for development of software (Mickeyl for example),
some use it to build software for distribution users (Koen), some use it
for different purposes (me for example). It is hard to make all of them
happy with each commit. This is .dev tree - things will break and we can
not stop it (we have stable/2009 for not breaking changes).
The real problem is not how to keep quality after each commit but how to
keep it overall. If something break do not automatically shout "you
moron, you broke OE" - it is not SouthPark and OE is not Kenny. So when
problem shows we need to discuss how to fix it instead of shouting at
each other. Otherwise it is no longer fun but just work. And when it is
just work then...
JID: hrw at jabber.org
More information about the Openembedded-devel