View Single Post
Posts: 339 | Thanked: 1,623 times | Joined on Oct 2013 @ France
#1
Hello,

In these difficult times, I have seen a call to help funding the mer infrastructure (https://twitter.com/locusf/status/668409070643257344).

At the same time, I have seen a comment on a blog, stating that developing mer is redondant with what Yocto provides (Linux, Wayland, Qt, ...), but with Yocto supported by the linux foundation and industrial companies.

* I never thought of it that way, but indeed, what is the difference between Mer and Yocto ?
* What does Mer provides that Yocto doesn't ?
* Is that only a schedule consequence that Yocto didn't exist or was not as supported as it is now, when Mer was chosen/started ?
* Isn't it too late to rebase Sailfish OS on top of Yocto ? The hardware adaptation layer would need a lot of work propably for the Jolla, but the upper stack (Nemo, Silica and other sailfish OS packages) shouldn't need that much changes than writing new bitbake recipes, isn't it ?
* Would switching to Yocto make it faster to port it to future hardware, as a lot are supported now ? Maybe not as good support on multimedia models like Mediatek then industrial platforms like iMx6 and SAMA5 ?


Feel free to explain with technical details, I uses Yocto a bit at work, and tried porting Sailfish to xt897 using the HADK, so I should be able to follow (even if not being able to do it by myself...).

Thanks !
 

The Following 11 Users Say Thank You to Zeta For This Useful Post: