On Fri, 2015-03-06 at 10:27 +0100, Xavier Roche 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.
I was actually wondering about that. You already updated the "tizen" branch while still working on fixes for that update in your sandbox branch. That means anyone checking out meta-tizen now gets something which is broken. It is also not clear how the update was produced. Is it the result of a spec2yocto run (if so, which config was used?), with or without manual fixes? I wonder whether this could have been done using the "upstream" and "tizen-merged" branches. I can imagine that there would have been more merge conflicts than usual, but at least it would have been obvious where previously applied fixes need adapting. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
