[oe] [oe-commits] Koen Kooi : Revert "ecore: catch up with the new SONAMEs; move to autosplitting"
Michael 'Mickey' Lauer
mickey at vanille-media.de
Sat Apr 25 19:44:45 UTC 2009
On Saturday 25 April 2009 20:44:59 Graeme Gregory wrote:
> Michael 'Mickey' Lauer wrote:
> > On Saturday 25 April 2009 20:17:22 Otavio Salvador wrote:
> >> This all is not a justification to break the whole World at dev. dev
> >> will be the basis of next stable, and even more, it is the source of
> >> changes for stable. So if we mess it up we'll end up with an very
> >> difficult to maintain stable branch and an unusable dev.
> >
> > Yes, and I agree with all that, however there is the need to balance
> > between breaking everything and letting everything through. If -- like it
> > is happening right now -- people are paranoid about upgrade paths, then
> > .dev moves to something where no actual development happens.
> >
> > If you want to move forward, you will have to allow breakage now and
> > then. This is the way with all projects. If you don't allow that, people
> > will move elsewhere with their contributions and .dev will get stale
> > rather than stable.
>
> In this case was it actually necessary to change the names?
Yes. Upstream changed their SONAME in a freaky way, hence we needed to catch
up.
> I'm afraid I try and ignore E stuff as much as possible so I am totally
> unclear about its state of development.
All was clear and calm until last week. It took Angus two days to come up with
a solution in MS5.5 were E-Wm was starting again and everything necessary was
installed in the image (RRECOMMENDS and friends...). His solution involved
turning off the debian renaming for each and every package -- a solution that
works fine but that was unacceptable for me in .dev -- hence I went forward and
worked on a better solution that involved keeping debian naming and even
removed the verbosity in ecore.inc.
This solution has now been reverted for the sake of the upgrade path. And just
for the records, the technical issue wasn't the reason for me leaving the OE
core team and resigning from all duties -- it was the way how this situation
was handled. Again the core team pretty much stood watching in apathy and let
the most vocal decide on his own, letting him carry his own way again.
:M:
More information about the Openembedded-devel
mailing list