From Fedora Project Wiki
No edit summary |
(add mconf, gypsy comments) |
||
| Line 6: | Line 6: | ||
* Network Mgmt (Fedora:[http://projects.gnome.org/NetworkManager/ NetworkManager] vs MoblinCore:Connman) | * Network Mgmt (Fedora:[http://projects.gnome.org/NetworkManager/ NetworkManager] vs MoblinCore:Connman) | ||
* Configuration management (Fedora:GConf and GSettings upstream work vs [http://moblin.org/category/tags/mconf MoblinCore:mconf]) | |||
== Unknown convergence == | == Unknown convergence == | ||
| Line 17: | Line 18: | ||
* Content Mgmt (MoblinCore:libbickley) | * Content Mgmt (MoblinCore:libbickley) | ||
* Location (MoblinCore:gypsy) | * Location (MoblinCore:gypsy) -- gypsy is already available through Geoclue and used in the desktop (gnome-bluetooth, Empathy, etc.) ([[User:Hadess]]) | ||
Revision as of 15:31, 22 September 2009
Moblin Core Merge
This is a wiki page about an ongoing project to ensure that the Fedora core OS (as defined by comps) and Moblin Core are in sync as much as possible.
Will not converge
- Network Mgmt (Fedora:NetworkManager vs MoblinCore:Connman)
- Configuration management (Fedora:GConf and GSettings upstream work vs MoblinCore:mconf)
Unknown convergence
- Init (MoblinCore: fastinit vs Fedora:Upstart)
- System crash handling (MoblinCore:corewatcher), Fedora:ABRT)
To evaluate for Fedora Desktop
I think most of these are DBus services, so they'll get activated on demand. Should we need to ensure we have an RPM dependency even if nothing uses them right now in the default Fedora desktop?
- Content Mgmt (MoblinCore:libbickley)
- Location (MoblinCore:gypsy) -- gypsy is already available through Geoclue and used in the desktop (gnome-bluetooth, Empathy, etc.) (User:Hadess)