Re: [yocto] Migrate, or not Migrate, that's the question!!!

2016-02-02 Thread Diego Sueiro
On 2 February 2016 at 08:40, Diego Sueiro wrote: > Khem, > > On 1 February 2016 at 18:34, Khem Raj wrote: > >> >> I think you have to think about what you are getting into. You are trying >> to mix quite two different things are create third one. If I were you, I >> would just >> keep myself syn

Re: [yocto] Migrate, or not Migrate, that's the question!!!

2016-02-02 Thread Diego Sueiro
Khem, On 1 February 2016 at 18:34, Khem Raj wrote: > > I think you have to think about what you are getting into. You are trying > to mix quite two different things are create third one. If I were you, I > would just > keep myself synced with upstream as much as I could, Don’t look one way, > yo

Re: [yocto] Migrate, or not Migrate, that's the question!!!

2016-02-01 Thread Khem Raj
> On Feb 1, 2016, at 6:18 AM, Diego Sueiro wrote: > > Bryan, > > > On 28 January 2016 at 13:49, Bryan Evenson > wrote: > In my opinion, I think in the long term it would be easier to make a clean > break. Start with a recent branch, like Jethro, get a minimal

Re: [yocto] Migrate, or not Migrate, that's the question!!!

2016-02-01 Thread Diego Sueiro
Bryan, On 28 January 2016 at 13:49, Bryan Evenson wrote: > In my opinion, I think in the long term it would be easier to make a clean > break. Start with a recent branch, like Jethro, get a minimal image to > build for your hardware and then add your own layer with your proprietary > recipes.

Re: [yocto] Migrate, or not Migrate, that's the question!!!

2016-01-28 Thread Bryan Evenson
...@yoctoproject.org] On Behalf Of Diego Sueiro Sent: Monday, January 25, 2016 4:41 AM To: yocto@yoctoproject.org Subject: [yocto] Migrate, or not Migrate, that's the question!!! Hello folks, I'm in a project that uses openembedded-classic and Arago stuff to build the product's

[yocto] Migrate, or not Migrate, that's the question!!!

2016-01-25 Thread Diego Sueiro
Hello folks, I'm in a project that uses openembedded-classic and Arago stuff to build the product's image. A lot of problems have been raised in relation to build time, dependencies handling, integrating new recipes, recipes tweaks etc. We are evaluating the possibility to migrate to Yocto Proje