[oe] reverting some csets that kill package upgrade paths

[Tom Rini]

On Fri, Apr 24, 2009 at 12:14:13PM -0700, Tom Rini wrote:
> On Fri, Apr 24, 2009 at 09:03:18PM +0200, Koen Kooi wrote:
[snip]
> > Upgrade paths are the foundation of package management, breaking them is  
> > stabbing people using your binaries in the eye. Do you want to tell the  
> > companies evaluating OE using .dev that they can't use the feature  
> > anymore that drew them to OE, namely package management?
> >
> > If it's OK to break package management is it OK to break toolchains as  
> > well? If people can't use the resulting binaries it should be OK to  
> > break the compiler that would build them, right?
> >
> > Without upgrade paths OE is just buildroot with a really slow parser on top.
> 
> So it's not OK to say "Upstream changed things, and we're following suit
> here in the development line.  Over in the stable line we're adding the
> extra overhead to allow for a clean upgrade path".

To be clear going from stable/2009 to stable/2011 should work iff via
stable/2010.  And in stable/2011 we shouldn't have RCONFLICT/RPROVIDES
libwhatever-rename-happend-in-2009.  But I don't think updating dev on a
live system from a few months ago to a few months in the future has to
absolutely work with no human intervention.  It sounds like some apps
need to be rebuilt vs the new libraries or so and that's the problem.

-- 
Tom Rini