Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Tom Rini <trini@embeddedalley.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: reverting some csets that kill package upgrade paths
Date: Fri, 24 Apr 2009 12:24:35 -0700	[thread overview]
Message-ID: <20090424192435.GC15489@smtp.west.cox.net> (raw)
In-Reply-To: <20090424191413.GB15489@smtp.west.cox.net>

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



  reply	other threads:[~2009-04-24 19:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-24 17:32 reverting some csets that kill package upgrade paths Koen Kooi
2009-04-24 17:55 ` Philip Balister
2009-04-24 19:03   ` Koen Kooi
2009-04-24 19:14     ` Tom Rini
2009-04-24 19:24       ` Tom Rini [this message]
2009-04-24 19:47         ` Koen Kooi
2009-04-24 19:39       ` Koen Kooi
2009-04-24 19:32     ` Tom Rini
2009-04-24 19:48       ` Koen Kooi
2009-04-24 19:53       ` Koen Kooi
2009-04-25 20:40         ` Marcin Juszkiewicz
2009-04-24 20:40       ` Philip Balister
2009-04-27  3:22         ` Tom Rini
2009-04-25 21:18 ` Marcin Juszkiewicz
2009-04-25 21:37   ` Koen Kooi
2009-04-25 21:56     ` Marcin Juszkiewicz
2009-04-26  1:59       ` Carsten Haitzler
2009-04-26  9:27   ` Koen Kooi
2009-04-27  8:46     ` Marcin Juszkiewicz
2009-04-26  1:53 ` Carsten Haitzler
  -- strict thread matches above, loose matches on Subject: below --
2009-04-24 17:23 Koen Kooi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090424192435.GC15489@smtp.west.cox.net \
    --to=trini@embeddedalley.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox