Changes

Jump to navigation Jump to search
Line 46: Line 46:  
== What Sugar Services are not ==
 
== What Sugar Services are not ==
   −
* Sugar Services is not intended to cure all ills.
+
* It is ''not'' intended to cure all ills.
* It is not "must have" for activity developers; use it only if you really [[#Work_flows|need]] it.
+
* It is ''not'' "must have" for activity developers; use it only if you really [[#Work_flows|need]] it.
* Is is not a replacement for GNU/Linux distributions packaging efforts; Sugar Services places no need for special treatment regarding dependencies as part of the [[0.86/Platform_Components|Sugar Platform]].
+
* Is is ''not'' a replacement for GNU/Linux distributions packaging efforts; Sugar Services places no need for special treatment regarding dependencies as part of the [[0.86/Platform_Components|Sugar Platform]].
* It is not intended to be used to support large packages such as Qt that are not included in standard Sugar releases.  
+
* It is ''not'' intended to be used to support large packages (such as Qt or Firefox) that are not included in standard Sugar releases. Sugar Services should not be used to avert scenarios such as ''"It is too bad that you don't have Firefox-3.5 in your three-year-old distribution and cannot run last Browse activity."''' In such cases, we should require that users update their distribution and Sugar Platform to more recent versions.
 
  −
Sugar Services works in parallel with distributions. With Sugar Services, it is possible (and preferable) to reuse native packages when they are available. Sugar Services provides a convenient way to install such packages and thus avert scenarios such as ''"That's really too bad that you don't have Firefox-3.5 in your three-year-old distribution and cannot run last Browse activity, but we cannot package Firefox-3.5 for you, so please update your distribution and Sugar Platform to last versions."''
      
== Detailed Description ==
 
== Detailed Description ==

Navigation menu