Deciding between Buildroot & Yocto

Posted Apr 11, 2016 11:37 UTC (Mon) by BlueLightning (subscriber, #38978)
In reply to: Deciding between Buildroot & Yocto by HIGHGuY
Parent article: Deciding between Buildroot & Yocto

> Still, one must question if the addition of these debugging features aren't just a plaster on an open leg wound. One must truly
> understand how bitbake parses and operates, one must become very familiar with the layers used before you can effectively and
> efficiently make an image out of it. There's a very steep learning curve to go through to make a proper image. Apparently that's
> one of the prices to pay for the extreme flexibility it offers.

I think we do try to improve things where we can, and we've come a long way since the Yocto Project started - of course there's only so much you can do to simplify a complex system, and there's no denying that OE is complex. I know you've been a long-term user based on your comments here so if you have any suggestions on how we might improve we would definitely like to hear them.

> Another downside is that there's a ton of legacy. It's true that there are many layers and many packages in them. But you can
> scrap a lot of them as unusable as-is because they contain legacy cruft due to a lack of love and care.

"A lot of them"? Quality does vary across layers, that is true - it depends on how diligent the maintainer is. I know this is probably too small a space to get into specifics but can you elaborate on where you've found lack of maintenance?