On 12/15/10 05:14, Wichmann, Mats D wrote:
[email protected] wrote:
Em Terça-feira, 14 de Dezembro de 2010, às 16:45:28, Jechlitschek,
Christoph escreveu:
Hi all,
I was wondering if there exists a migration path from MeeGo 1.0 to
MeeGo 1.1 and later to MeeGo 1.2. This is very interesting for
companies that have devices in the field and want to push an upgrade
to the next higher version (instead of just an update within a
version).
Is it just a zypper dist-upgrade with new repositories?
Yeah, sounds about right. :-)
in theory, but things do change and I've certainly seen cases
on other distros where that doesn't work correctly. so the question
is, is version upgrading a supported target?
not currently supported....
I wrote a wiki page about how to do this manually (not that complex,
although non-trivial), and that works because `zypper dup` is pretty
intelligent.
The part that is missing to make this a trivial exercise (for an
end-user) is:
- adding the new keys (e.g. 1.1 keys) to the 1.0 repo (and having the
package that contains the 1.1 keys being SIGNED by the 1.0 signing keys).
- having an application install the new (e.g. 1.1) repo files
(meego-release.rpm from the 1.1 repo) and kicking off a dist-upgrade.
I suppose one could write a tiny Qt application that calls the right
packagekit methods in a few hours... it shouldn't be too hard :)
Auke
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
