All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bryan Evenson <bevenson@melinkcorp.com>
To: Diego Sueiro <diego.sueiro@gmail.com>,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Migrate, or not Migrate, that's the question!!!
Date: Thu, 28 Jan 2016 13:49:37 +0000	[thread overview]
Message-ID: <BLUPR0501MB18434F9CCFB9D423227C9F53BBDA0@BLUPR0501MB1843.namprd05.prod.outlook.com> (raw)
In-Reply-To: <CAMCfZKF6asR9ubz7+oKJQ6FCO8mM0ryUzq-WDBGf6AAp2+WeMw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2454 bytes --]

Diego,

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.

Regards,
Bryan

From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@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 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 Project (Openembedded Core). But some requirements MUST be met:

  *   eglibc (2.12), gcc (4.5.3), u-boot, kernel and other packages versions must have be maintained. We cannot update it versions since this product is in the field for a couple of years and it was heavily tested and certified.

I read some guidelines[1][2], but my main concern is if I'm going into a "can of worms", as most packages dating from 2011 and I do not know how much the OpenEmbedded-core is "coupled" to glibc and gcc versions, for example.


I think the ideal scenario is to use the most recent Yocto version and have all nice features available. Perhaps to achieve this I have to migrate first to "2011-1" branch of openembedded-core and have all packages versions and custom modifications ported to the new openembedded platform and then migrate to the a newer version.



I really appreciate if you guys have some thoughts, tips or some kind of information that can help me to take this decision and move forward.



[1] http://www.yoctoproject.org/docs/2.0/mega-manual/mega-manual.html#migration
[2] http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core



Regards,

--
*dS
Diego Sueiro

Administrator of Embarcados
www.embarcados.com.br<http://www.embarcados.com.br/?utm_source=assinatura_diego&utm_medium=e-mail&utm_campaign=Assinatura%20Email%20Diego>

[-- Attachment #2: Type: text/html, Size: 9719 bytes --]

  reply	other threads:[~2016-01-28 15:23 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 [this message]
2016-02-01 14:18   ` Diego Sueiro
2016-02-01 18:34     ` Khem Raj
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=BLUPR0501MB18434F9CCFB9D423227C9F53BBDA0@BLUPR0501MB1843.namprd05.prod.outlook.com \
    --to=bevenson@melinkcorp.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.