From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: upgrading from oe-classic to oe-core
Date: Thu, 03 May 2012 15:30:03 +0200 [thread overview]
Message-ID: <jnu18r$n5e$1@dough.gmane.org> (raw)
In-Reply-To: <4FA27A3F.60500@nedap.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 03-05-12 14:29, Jaap de Jong schreef:
>
>
> On 05/03/2012 01:40 PM, Frans Meulenbroeks wrote:
>> Op 3 mei 2012 13:29 heeft Jaap de Jong<jaap.dejong@nedap.com> het
>> volgende geschreven:
>>> Hi All, If I have devices running on oe-classic and I want to upgrade
>>> them to oe-core, will the upgrade be without worries? It will
>>> probably download all packages? Or do I have to takes special steps?
>> Depends on the devices and how well they are supported in yocto (e.g.
>> is there a bsp for them) And on the actual packages you want to have on
>> your device.
>>
>> If you have some recipes of your own, you definitely will have some
>> work upgrading these.
>>
> That part is clear! And I'm working on that right now.
>
> What I ment is: I have these devices with all those packages on them
> build with oe-classic. I would really like to have an idea what will
> happen when I do a 'opkg update ; opkg upgrade' on them. Anyone done
> that?
It won't work, various packages have been renamed, combined or split up. Not
to mention that the toolchains are vastly different.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org
iD8DBQFPoohbMkyGM64RGpERAvwaAJ9AbIIQLNmptpY6zCk7LcqKctebdwCeJydH
x9SAtsiTqH4kU3jwoqY/xRg=
=OW43
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2012-05-03 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 11:29 upgrading from oe-classic to oe-core Jaap de Jong
2012-05-03 11:40 ` Frans Meulenbroeks
2012-05-03 12:29 ` Jaap de Jong
2012-05-03 13:30 ` Koen Kooi [this message]
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='jnu18r$n5e$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox