I am not clear about the discussion also, please add me in the loop, thanks. As I mentioned in anothe thread about this special branch, I feel plain tizen_2.1/tizen_2.2 can also work. Please correct me if I am wrong.
thanks - jf.ding On Tue, Oct 08, 2013 at 12:27:29PM +0000, Kanevskiy, Alexander wrote: > On 10/8/13 15:14 , "Yin, Yan" <[email protected]<mailto:[email protected]>> > wrote: > > Hi Sasha, > > We do understand all Tizen 3.0 code line must use “tizen” branch, we always > keep it in mind and won’t violate it. > > This is to enable Tizen 3.0 image with Tizen 2.x content due to reality, EFL > and GStreamer are the two unlucky cases. To reach the goal, either have to > fork a new git path, or reuse the same git repo with a specific branch. > > There has been long discussion on the pros/cons for both solution when we > enable Tizen 3.0 IA images, and below solution is agreed by > Anas/Praj/BingWei/etc, actually Anas suggested the tizen_2.1_compat branch > name :), then we spent great efforts to make it happen. > > > This would create issues for "local full build" feature, where manifest files > would specify same repo twice with same path but different revisions. > Did somebody from dev tools team participated in discussion and in > verification of that approach ? > > Any more background information you’d like to know, please let me know and I > can send you directly. :) > > Please, send to me thread where it was discussed. > > > Thanks, > Yan > > From: Kanevskiy, Alexander > Sent: Tuesday, October 08, 2013 7:54 PM > To: Yin, Yan; [email protected]<mailto:[email protected]> > Cc: Karur Mohan, Prajwal > Subject: Re: [Dev] Please use "tizen_2.x_compat" branch for Tizen 3.0 image > enabling with Gstreamer 0.10 > > On 10/8/13 14:47 , "Yin, Yan" <[email protected]<mailto:[email protected]>> > wrote: > > Please, don't create mess with a branches. > Tizen 3.0 codeline must use "tizen" branch for all projects that is part of > it. > > Hi, > > We’ll have another thread discussing the full gstreamer 0.10.x to 1.x > upgrading plan. This thread will focus on discussing how to enable functional > Tizen 3.0 image for both ARM and IA, with gstreamer 0.10.x actually used. > > Gstreamer upgrading from 0.10.x to 1.x is a huge effort, which can be break > down into 3 categories by packages: > > 1) Upstream gstreamer packages: Tizen specific gstreamer 0.10.x patches > need porting to those upstream 1.x gstreamer and gst-plugins-xxx packages. > > l > gstreamer/gst-plugins-base/gst-plugins-good/gst-plugins-bad/gst-plugins-ugly/gst-libav/gst-omx/gstreamer-vaapi, > etc. > > 2) Tizen gstreamer plugins: Tizen specific gstreamer 0.10.x plugins > need porting to 1.x API. > > l gst-plugins-ext0.10/gst-plugins-e4x12/ gst-plugins-fimcconvert/ > gst-plugins-s5pc2xx/gst-plugins-atomisp/gst-plugins-emulator/gst-plugins-audio-hwdec, > etc. > > 3) Tizen framework packages: Tizen framework packages who use 0.10 > gstreamer plugins and APIs need porting to 1.x API. > > l gst-plugins-ext0.10/gst-plugins-e4x12/ gst-plugins-fimcconvert/ > gst-plugins-s5pc2xx/gst-plugins-atomisp/gst-plugins-emulator/gst-plugins-audio-hwdec, > etc. > > Previously, we have been using tizen_2.1_compat branch of > platform/upstream/gst-plugins-xxx for Tizen 3.0 IA image enabling which > proves to work smoothly , now Tizen 2.2 is released and we also need Tizen > 3.0 ARM images, we need some changes here: > > 1) Upstream gstreamer packages: rename tizen_2.1_compat branch to > tizen_2.x_compat branch, change GIT<->OBS mapping correspondingly, so that > tizen_2.x_compat branch package is submitted to OBS with package name > suffixed with 0.10, these 0.10 packages will co-exist with those 1.x API > gstreamer packages in same OBS project (and might even in same image during > the migration). > > 2) Tizen gsteamer plugins: populate tizen branch with tizen_2.2 branch > content. > > 3) Tizen framework packages: populate tizen branch with tizen_2.2 > branch content. > > @Praj, we need your help for below things, many thanks in advance! > > 1) please remove below forked git path which is useless, we will use > the tizen_2.x_compat branch of platform/upstream/gst-plugins-xxx instead. > profile/mobile/gst-plugins-bad0.10 > profile/mobile/gst-plugins-base0.10 > profile/mobile/gst-plugins-ext0.10 > profile/mobile/gst-plugins-good0.10 > profile/mobile/gst-plugins-ugly0.10 > profile/mobile/gstreamer0.10 > profile/mobile/gstreamer0.10-ffmpeg > profile/mobile/gstreamer0.10-ffmpeg8 > profile/mobile/libmm-player > > > 2) please change GIT<->OBS mappging from previously > “tizen_2.1_compat<->Tizen” to “tizen_2.x_compat<->Tizen”. > > Regards, > Yan > > > > -- > Best regards, Alexander Kanevskiy. > > > -- > Best regards, Alexander Kanevskiy. > --------------------------------------------------------------------- > Intel Finland Oy > Registered Address: PL 281, 00181 Helsinki > Business Identity Code: 0357606 - 4 > Domiciled in Helsinki > > This e-mail and any attachments may contain confidential material for > the sole use of the intended recipient(s). Any review or distribution > by others is strictly prohibited. If you are not the intended > recipient, please contact the sender and delete all copies. > > _______________________________________________ > Dev mailing list > [email protected] > https://lists.tizen.org/listinfo/dev _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
