Hi Jinkun, Sehong, For arm-wayland images on Tizen:Common, as pointed before, the following patch https://review.tizen.org/gerrit/#/c/23955/1 was not reviewed by other people and was merged without waiting. When the submission came in the queue, I looked at the commit and rejected it because the package group "Common Ref M0" has a cryptic name.
Furthermore, the packages included in the group are not ARM specific and may also land in other images. In one word, I would have put a -1 or a -2 on this commit if I had time to do so and have a chance to correct the patch. I already made all the necessary comments 1) in the repa reject notification and 2) in the review on gerrit but didn't get your feedback. Please note that I'm currently reworking profile/common/meta to ensure the migration of common (shared) groups definitions to platform/upstream/meta-generic. See https://bugs.tizen.org/jira/browse/PTREL-807 for details. So I'll probably push-force to remove the latest commit and sync packages names in meta-generic with images definitions in common/meta. I'll also add the arm image as you did and define the add the needed package groups. Regards, -- Stéphane Desneux Intel OTC - Vannes/FR gpg:1CA35726/DFA9B0232EF80493AF2891FA24E3A2841CA35726 On 10/07/2014 12:39, Dominig Ar Foll wrote: > 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 > > _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
