From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: transitional packages
Date: Thu, 27 Mar 2014 12:33:39 +0100 [thread overview]
Message-ID: <20140327113339.GO3709@jama> (raw)
In-Reply-To: <5333F1AC.4060807@nedap.com>
[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]
On Thu, Mar 27, 2014 at 10:38:52AM +0100, Jaap de Jong wrote:
> Hi All,
>
> for one project I'm still using oe-classic.
> Would like to upgrade that!
> I know a simple update will not work because (among others?) package
> names are changed.
> Is there any effort made to create transitional packages?
I don't know about any.
> If not, would it be a tough job?
Yes, maybe not so bad if you have exactly one starting point and one
final, but to provide upgrade path from "some" state of binary feeds in
oe-core to "some" state of binary feeds built with oe-core is very close
to impossible (as you cannot test every combination).
Some versions went backwards, you need to migrate LOCALCOUNTs to PRSERV
db a lot of packages were renamed or removed without replacement (so
they will be stuck in your target image unless you explicitly RCONFLICT
RREPLACE them from your transitional package), there are upgrade path
issues even between oe-core revisions.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2014-03-27 11:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 9:38 transitional packages Jaap de Jong
2014-03-27 11:33 ` Martin Jansa [this message]
2014-03-28 7:12 ` Jaap de Jong
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=20140327113339.GO3709@jama \
--to=martin.jansa@gmail.com \
--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 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.