All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Diego Sueiro <diego.sueiro@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Migrate, or not Migrate, that's the question!!!
Date: Mon, 1 Feb 2016 10:34:24 -0800	[thread overview]
Message-ID: <3BA28CC0-59D4-4013-BD2E-3CAE31B1159D@gmail.com> (raw)
In-Reply-To: <CAMCfZKHu1YtfYq3GH2R8drMSnFWwYzD8VPs2nwQcGTg4LJr3Mg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2340 bytes --]


> On Feb 1, 2016, at 6:18 AM, Diego Sueiro <diego.sueiro@gmail.com> wrote:
> 
> Bryan,
> 
> 
> On 28 January 2016 at 13:49, Bryan Evenson <bevenson@melinkcorp.com <mailto:bevenson@melinkcorp.com>> 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.  I think that will be a lot easier than trying to get oe-core working with 5+ year old versions of gcc and eglibc.  Yes, that would mean additional testing, but it may be less testing/integration than you are currently doing just trying to keep your current image maintained.
> 
> 
> 
> 
> Thanks for your opinion.
> 
> But unfortunately, updating the packages is out of scope in this moment since the product is certificated and doing this will require a new process.

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, you have to look into time and effort you will spend on maintaining this new
jargon for years to come.

> 
> Maybe I can use the Arago External Pre-built Binary Toolchain (2011-09)[1] in which is supported by TI until daisy branch[2].
> 
> 
> [1] - http://software-dl.ti.com/sdoemb/sdoemb_public_sw/arago_toolchain/2011_09/index_FDS.html <http://software-dl.ti.com/sdoemb/sdoemb_public_sw/arago_toolchain/2011_09/index_FDS.html>
> [2] - http://arago-project.org/git/?p=meta-arago.git;a=tree;f=meta-arago-extras/conf/distro/include;h=23e7bcba85ab80e4bf813fd43f64c61a12ba3f0a;hb=refs/heads/daisy <http://arago-project.org/git/?p=meta-arago.git;a=tree;f=meta-arago-extras/conf/distro/include;h=23e7bcba85ab80e4bf813fd43f64c61a12ba3f0a;hb=refs/heads/daisy>
> 
> 
> Regards,
> 
> --
> *dS
> Diego Sueiro
> 
> Administrador do Embarcados
> www.embarcados.com.br <http://www.embarcados.com.br/?utm_source=assinatura_diego&utm_medium=e-mail&utm_campaign=Assinatura%20Email%20Diego>
> 
> /*long live rock 'n roll*/
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


[-- Attachment #1.2: Type: text/html, Size: 4367 bytes --]

[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]

  reply	other threads:[~2016-02-01 18:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25  9:40 Migrate, or not Migrate, that's the question!!! Diego Sueiro
2016-01-28 13:49 ` Bryan Evenson
2016-02-01 14:18   ` Diego Sueiro
2016-02-01 18:34     ` Khem Raj [this message]
2016-02-02  8:40       ` Diego Sueiro
2016-02-02  9:07         ` Diego Sueiro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3BA28CC0-59D4-4013-BD2E-3CAE31B1159D@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=diego.sueiro@gmail.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.