Changes

Jump to navigation Jump to search
Line 34: Line 34:  
So, developers use a set of services that have theirs own API changes based schedules. Existed glucose could be treated as a big service and splited to several components but thats not a task for this proposal. Instead, it's about proposing basic infrastructure of Sugar Services and several services that are not part of glucose.
 
So, developers use a set of services that have theirs own API changes based schedules. Existed glucose could be treated as a big service and splited to several components but thats not a task for this proposal. Instead, it's about proposing basic infrastructure of Sugar Services and several services that are not part of glucose.
   −
The corner stone of Sugar Services proposal is Saccharin service. This service provides installing/upgrading mechanism for all other services. The rest of services is just variety of sugar libraries/dbus-services.
+
The corner stone of Sugar Services proposal is Saccharin service. This service provides installing/upgrading(via [[Zero Install integration]]) mechanism for all other services. The rest of services is just variety of sugar libraries/dbus-services.
    
=== List of services ===
 
=== List of services ===

Navigation menu