On 26 July 2013 11:39, Laszlo Papp <lp...@kde.org> wrote: > If you do not trust Arch, you can use something else. That does not mean > there would not be people who update (daily for instance) and fix the issues > coming up.
And that already happens - I'm running Debian Unstable, others may be running Rawhide, or Arch. You'll see numerous commits in master fixing issues where updates on the *host* have broken the build[1]. Let's imagine we are testing Arch or any other rolling/development distribution. The day we freeze oe-core 1.5 we could write that Arch Linux is a tested and supported distribution, and we release. A week later Arch integrates (for example) a newer gcc that introduces some new errors, so we can't bootstrap anymore. The documentation says that Arch is tested, yet someone using Arch will discover that it doesn't work. They'll rightly complain that the documentation is wrong, and Arch doesn't work. Of course if ArchLinux decided to have a maintained stable branch, then that would be something worth testing on. Ross [1] The latest I can recall of the top of my head is 8db36429ef328b97340ee1d9fc2e697cfdd68bff. _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
