Should BusyBox and uClibc also make a "flag version" like Embedded Linux?

[Peter Korsgaard]

>>>>> "Will" == Will Newton <will.newton at gmail.com> writes:

Hi,

 Will> I'm not sure that there's quite the same need for flag versions.
 Will> Upgrading a kernel can cause lots of subtle changes in how the
 Will> system behaves and incur a lot of effort in updating out of tree
 Will> drivers, whereas swapping a new BusyBox in has been very painless
 Will> in our experience. I don't recall whether we have ever had any
 Will> issue other than perhaps having to update the config file we use.

Indeed. HW specific stuff like the kernel and bootloader can be painful,
but higher level stuff usually aren't.

 Will> To be honest I've experienced much larger problems with toolchain and
 Will> build system upgrades rather than uClibc and BusyBox version bumps.

Which makes sense as you then normally upgrade the version of several
packages at once, so the amount of potential problems get multiplied.

-- 
Bye, Peter Korsgaard