On Thu, 27 Nov 2014 08:09:50 +0100 Kévin THIERRY <[email protected]> said:
> > On 11/27/2014 12:18 AM, Carsten Haitzler (The Rasterman) wrote: > > On Wed, 26 Nov 2014 15:21:07 +0100 "Dominig ar Foll (Intel OTC)" > > <[email protected]> said: > > > >> Hello, > >> > >> as you know we are aligning as much as we can Tizen packages version > >> with Yocto 1.7 packages version. > > nope. i didn't know. when/where was this discussed? anyway... > In this mailing list (dev): > https://www.mail-archive.com/[email protected]/msg04451.html oooh.. while i was busy in conference madness. that's why i missed it :) > http://permalink.gmane.org/gmane.comp.handhelds.tizen.devel/4706 > http://comments.gmane.org/gmane.comp.handhelds.tizen.devel/4912 > > > > does this mean we are dropping GBS then as we'll build with OE? > Yes but OBS build will still be supported as an alternative. I'm not > sure if GBS will still be supported but it can make sense since OBS is > still supported... why bother? the OE build is a clean proper cross-compile build with no need for qemu or misc binary emulation... no root needed. :) much nicer. > >> The goal is to increase portability of Tizen on multiple platforms while > >> reducing the maintenance burden on common packages. > >> > >> Once that this full alignment will be done, Tizen Common will represent > >> about 150/200 packages (today its just bellow a 1000) on top of a > >> standard Yocto/Poky reference. > >> These specials will mostly be related to : > >> - security and data privacy > >> - advanced communications > >> - Web run time > >> - App development and execution FW. > >> > >> The first step is to align the packages version and when possible the > >> patch level. > >> > >> In order to achieve that goal Kevin has tracked all the delta and has > >> created a bug for each package that requires changes. > >> The default mode has been to up either Yocto or Tizen which ever was > >> behind. > >> > >> Please note that while we have a strategic agreement to align on Yocto > >> package, maintainer needs to get and agreement via the Dev mailing list > >> to vary from the targeted version. > >> As usual, the requirement to derive will have to be justified. > >> When it will make sense we will force Yocto project to re-align on the > >> newly agreed release. > >> > >> I rely on the good behaviour of all of you, but in order to stop any non > >> agreed version to enter the system by error, I will also ask to Stéphane > >> (release engineer for Common) to reject any package change which jumps > >> to a non agreed version. > >> > >> I remember that on the mailing list "who says nothing agrees", but in > >> order to give time to get feedback, a delay of 1 full worked day for > >> small changes and 3 for larger should be respected. > >> Any structural change (e.g. systemd or glib) should give a full week for > >> feedback. > >> > >> Kevin maintains a shared document which allow to follow progress on that > >> initiative, please feel free to get a look. For those how cannot access > >> shared drive, I have added a printout of today status to this mail. > >> > >> Enjoy your day. > >> > >> -- > >> Dominig ar Foll > >> Senior Software Architect > >> Open Source Technology Centre > >> Intel SSG > >> > > > > _______________________________________________ > Dev mailing list > [email protected] > https://lists.tizen.org/listinfo/dev -- Carsten Haitzler (The Rasterman) <[email protected]> _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
