Hi, I can only strongly agree with Stephane, non respect of the process creates non cnstructive mess which are penalising all of us. In the case of Common it's even worse, as it affects each derived Profiles and architectures.
We have been looking for the days on the best model to add X11 to Common without letting X and Wayland package request mix up silently like it used to be in the past. It took a long time to clear those silent package mixing issues and we do not want them back. Loading undesired and unused lib in an embedded OS is not good and shall be avoided. The X enabling investigated model (in a private OBS to avoid to break any hot projects relying on a working Common) is based on the use of a project Conf which will create invalid calls to packages if a request to an X11 dependency is done in a Wayland repo and vice versa for X. We will propose our model in a few days in this list, as soon as we will have checked that it can work, and will call for feed back before implementing in agreement with all involved parties. In the mean time, we need to go back to the previous model where Common was building clean which is a pure loss of time. Regards -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
