[oe] reverting some csets that kill package upgrade paths
Tom Rini
trini at kernel.crashing.org
Mon Apr 27 03:22:20 UTC 2009
On Fri, Apr 24, 2009 at 04:40:42PM -0400, Philip Balister wrote:
> 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).
>
> I disagree. Angstrom is usable and depends on stable having sane upgrade
> paths as a community supported distro.
The key being stable. If I wasn't clear, a feed based on .dev is most
certainly random. A feed for a specific release would hopefully not be
based on .dev. A company working with Angstrom is feasible and would be
what I said :)
--
Tom Rini
More information about the Openembedded-devel
mailing list