Carlsen,
we need your advise for building Common.
The hack done in Tizen 2 for Mobile is not a legacy that we can afford
to assume in the Common project.
That is the issue of the mobile team who will be in charge of the move
from Tizen 2 to Tizen 3.
In view of that position what is your advise ?
Dominig ar Foll
Senior Software Architect
Open Source Technology Centre
Intel SSG
Le 30/07/2014 16:20, Carsten Haitzler (The Rasterman) a écrit :
On Wed, 30 Jul 2014 15:36:39 +0200 Stéphane Desneux
<[email protected]> said:
Hi Carsten,
Is Enlightenment 0.18.7 a better candidate ?
no. e17. as of e18 compositor is no longer a module. this totally kills the
compositor module fork of e's original compositor that was done for e17 and
tizen 2.x - this needs a re-do/design. this also changes how clients/borders
are handled api-wise.
It's not the latest one but it's far more recent than the 0.17.4 on
tizen git. We took this version because it was quite aligned with EFL
1.9.3 which is the current EFL version on Tizen:Common.
With these details, is it still a bad idea ? :)
only if you want to break tizen mobile entirely (as a mobile style ui - apps
will still display - just in windows) - then sure. go for it. then also remove
all the custom samsung e profile packages and config and go back to vanilla
enlightenment - then no problems. :) you definitely then want to nuke the tizen
elementary theme too and go back to vanilla as well. :) if you do this then may
as well go for git master. :)
--
Stéphane Desneux
Intel OTC - Vannes/FR
gpg:1CA35726/DFA9B0232EF80493AF2891FA24E3A2841CA35726
On 30/07/2014 14:37, Carsten Haitzler (The Rasterman) wrote:
On Wed, 30 Jul 2014 12:35:39 +0200 Stéphane Desneux
<[email protected]> said:
bumping to enlightenment upstream is going to be... bad at this stage. hold
on that for the time-being.
Hi Boram,
I updated our project with the 4 packages you updated.
1 new error occured, on xf86-video-intel (which is not up to date
probably).
Also, what happens for these remaining packages:
https://github.com/Tarnyko/enlightenment.git tizen
https://github.com/Tarnyko/xf86-video-intel.git tizen
https://github.com/Tarnyko/glproto.git
5903b304417886de32ad620ff8874998ddee4254
I think we should still bump them all. Your opinion ?
--
Stéphane Desneux
Intel OTC - Vannes/FR
gpg:1CA35726/DFA9B0232EF80493AF2891FA24E3A2841CA35726
On 29/07/2014 14:49, Boram Park wrote:
Hello Stephane
Today, I upgraded below 4 git repos to rebase xorg-server to 1.16. All
patches are pushed in "devel/x11" branch.
platform/upstream/xorg-server
platform/upstream/xproto
platform/upstream/fontsproto
platform/upstream/libXfont
Please check wethere there are any issues in your side. If no issue,
I'll send SRs together when I send SRs of x11 integration work.
Regards
Boram
------- *Original Message* -------
*Sender* : Stéphane Desneux<[email protected]>
*Date* : 2014-07-29 16:46 (GMT+09:00)
*Title* : Re: [Dev] Common/X11 schedule
Boram,
No problem for patches. Merging into tizen branch makes just things
easier (we can compare project manifests, submit diffs etc. easily)
FYI: to submit multiple packages at the same time on Tizen:Common,
please use 'group submissions'.
See: §3.1.2 on
https://source.tizen.org/documentation/developer-guide/getting-started-guide/contributing-code-tizen
for guidelines
This way, all 'related' packages that depend on each other will rebuild
as a whole. If the result is ok (seen in prerelease project), I can
accept the submission and bump all packages in the main project.
Thanks
--
Stéphane Desneux
Intel OTC - Vannes/FR
gpg:1CA35726/DFA9B0232EF80493AF2891FA24E3A2841CA35726
On 29/07/2014 08:39, Boram Park wrote:
Hello José and Stephane.
[just go to the branch tizen, how?]
I didn't merge devel/x11 to tizen branch. just created new patch for
tizen branch.
It seems to make you confused. Actually both branches have exactly same
patch.
BTW, I'll merge devel/x11 to tizen branch.
And, I didn't send SRs yet.
I concern that my SRs can be rejected by the maintainer of Tizen:Common
project. my SR will be able to be failed to build without other my SRs
becuase of build dependency.
So far I saw many reject message becuase of build fail. So we are going
to send SRs after fixing all build-errors in staging project and merging
all our work to tizen branch.
Anyway our all patches have been merged to tizen branch
[Diverging that have to be merged]
[Diverging, to be checked]
[Only of our side]
[Crosswalk compiled without scim]
Above 4 entries seems OK. And gl issue of arm-x11 repo is solved when I
take your patch for SDL and mesa. Thx.
Regards
Boram
------- *Original Message* -------
*Sender* : Jos� Bollo
*Date* : 2014-07-26 01:23 (GMT+09:00)
*Title* : Re: Re: [Dev] Common/X11 schedule
Please find here the real final report
BR
josé
On ven, 2014-07-25 at 18:22 +0200, José Bollo wrote:
Hello Boram,
I just finished the report (see joined).
You will find this entries:
[nothing to do, already at the good revision]
The branch tizen is already at the good revision for x11 that is already
accepted by OBS since long time.
[just go to the branch tizen, how?]
The branch tizen is already at the good revision for x11 but was never
accepted nor submitted, there is a workflow problem.
[Diverging that have to be merged]
mesa
[Diverging, to be checked]
SDL
[Only of our side]
libva
[Crosswalk compiled without scim]
crosswalk.
[Bumped on github for upgrading xserver]
An effort for upgrading xorg-server to 1.15.99.
Part of it may be used for bumping to xorg-server 1.16
Please check with Stephane for further work because I leaving this
evening for few weeks.
Best regards
José
------------------------------------------
Boram Park
Senior engineer
SAMSUNG ELECTRONICS CO.,LTD
E-Mail : [email protected]
------------------------------------------
Boram Park
Senior engineer
SAMSUNG ELECTRONICS CO.,LTD
E-Mail : [email protected]
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
