From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: reverting some csets that kill package upgrade paths
Date: Fri, 24 Apr 2009 21:48:02 +0200 [thread overview]
Message-ID: <gst51i$67b$2@ger.gmane.org> (raw)
In-Reply-To: <20090424193245.GD15489@smtp.west.cox.net>
On 24-04-09 21:32, Tom Rini wrote:
> On Fri, Apr 24, 2009 at 09:03:18PM +0200, Koen Kooi wrote:
>
>> 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?
>
> Red Herring. No commerical device is going to point to some random feed
> and just hope things work out fine. No, they're going to point at their
> supported feeds with updates they've tested and fixed any bugs that they
> happened to have found (and pushed back because they're Good Guys).
>
next prev parent reply other threads:[~2009-04-24 19:54 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
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 [this message]
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='gst51i$67b$2@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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