5,705
edits
Changes
Platform Team/Package Management System (view source)
Revision as of 09:22, 22 December 2009
, 09:22, 22 December 2009→What Sugar Services are not: expose Services possibility to reuse native not only SP packages
* It 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 Sugar 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 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.
* It is ''not'' intended to be used to support large packages (such as Qt or Firefox) in parallel with distributions. 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.
== Detailed Description ==
== Detailed Description ==