Xavier, So I have pushed all meta-tizen related changes to sandbox. Few of my changes require discussions. So It is interesting to get feedback.
With best regards, On Fri, Mar 6, 2015 at 3:18 PM, Vitaly Chernooky < [email protected]> wrote: > So for scm/bb/meta-tizen project my sandbox is sandbox/vitaly2014/tizen. > Currently package my changes for it. > > With best regards, > > On Fri, Mar 6, 2015 at 11:43 AM, Xavier Roche < > [email protected]> wrote: > >> Sure Vitaly, >> >> The only command you have to care about to create such a sandbox is: >> >> git push origin HEAD:sandbox/$gerritusername/$nameofyoursandbox >> >> You could then push whatever you want in this sandbox... >> Don't hesitate to call me if any problem... >> >> Xavier >> >> -- >> Xavier Roche >> Intel Open Source Technology Center >> >> >> On 06/03/2015 10:34, Vitaly Chernooky wrote: >> >> Xavier, >> >> On Fri, Mar 6, 2015 at 11:27 AM, Xavier Roche < >> [email protected]> wrote: >> >>> Hi all, >>> >>> Sorry for the delay, >>> >>> Basically, I share the same point of view as Patrick... >>> Using extraconf.inc files was a way to modify recipes without touching >>> the auto-generated files ( *_git.bb, *.bb). >>> Historically this auto-generation was useful for massive packages >>> synchronisation... >>> But now we get more and more closer to what the official tizen Common >>> release provides. >>> >>> Vitaly, for your information, I am currently working on the last >>> synchronisation with the in coming Tizen Common Q1 release. >>> Since some major features have disappeared/changed/appeared from our >>> last release, and since some important package bumping have to be applied, >>> I would recommend you to push your current work in a sandbox. >>> Doing so, you should then be able to easily rebase your sandbox on the >>> release I am about to publish next week. >>> >>> We could then discuss to what extent / how your work could be integrated >>> in meta-tizen... >>> >>> Does that seem acceptable to you? >>> >> >> Yes, it is acceptable for me, but in the past i have never used >> workflow with sandboxing so i need some guidance. Could you provide an >> example of push command? >> >> With best regards, >> >> >>> Regards, >>> >>> Xavier >>> >>> -- >>> Xavier Roche >>> Intel Open Source Technology Center >>> >>> >>> On 06/03/2015 09:51, Patrick Ohly wrote: >>> >>> On Thu, 2015-03-05 at 16:59 +0100, Baptiste Durand wrote: >>> >>> Hi >>> >>> >>> What he would like to say is to put your changes into *-extraconf.inc >>> files >>> ie >>> here : >>> crosswalk-thirdparty-extraconf.inc or crosswalk-extraconf.inc >>> >>> This is how it was done traditionally. But as I explained when >>> announcing the tizen-distro snapshot for IVI, that approach has several >>> drawbacks: often, when only having to change one line, one has to copy a >>> whole chunk of code from .inc into -extraconf.inc and then modify it >>> there. The result is that git is unable to show that diff, and when >>> updating the auto-generated .inc later one there is the risk that more >>> recent code is not used because of the copied, stale code in >>> -extraconf.inc. >>> >>> I used a different approach when putting together the IVI snapshot where >>> modifying the auto-generated .inc file is okay and encouraged. >>> >>> It comes down to what the current maintainer, Xavier, intends to do. >>> Xavier? >>> >>> >>> >>> >> >> >> -- >> *Vitaly Chernooky | Senior Developer - Product Engineering and >> Development* >> GlobalLogic >> P *+380.44.4929695 <%2B380.44.4929695> ext.1136* M *+380.63.6011802 >> <%2B380.63.6011802>* S cvv_2k >> www.globallogic.com >> >> http://www.globallogic.com/email_disclaimer.txt >> >> >> > > > -- > *Vitaly Chernooky | Senior Developer - Product Engineering and Development* > GlobalLogic > P *+380.44.4929695 ext.1136 <%2B380.44.4929695%20ext.1136>* M *+380.63.6011802 > <%2B380.63.6011802>* S cvv_2k > www.globallogic.com > > http://www.globallogic.com/email_disclaimer.txt > -- *Vitaly Chernooky | Senior Developer - Product Engineering and Development* GlobalLogic P *+380.44.4929695 ext.1136* M *+380.63.6011802* S cvv_2k www.globallogic.com http://www.globallogic.com/email_disclaimer.txt
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
