From Fedora Project Wiki
(add mconf, gypsy comments) |
m (internal link cleaning) |
||
| Line 10: | Line 10: | ||
== Unknown convergence == | == Unknown convergence == | ||
* Init (MoblinCore: [http://git.moblin.org/cgit.cgi/fastinit/ fastinit] vs Fedora:[ | * Init (MoblinCore: [http://git.moblin.org/cgit.cgi/fastinit/ fastinit] vs Fedora:[[Upstart|Upstart]]) | ||
* System crash handling (MoblinCore:[http://git.moblin.org/cgit.cgi/corewatcher/ corewatcher]), Fedora:[ | * System crash handling (MoblinCore:[http://git.moblin.org/cgit.cgi/corewatcher/ corewatcher]), Fedora:[[Features/ABRT|ABRT]]) | ||
== To evaluate for Fedora Desktop == | == To evaluate for Fedora Desktop == | ||
Latest revision as of 14:51, 18 September 2016
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)