Platform Team/Package Management System: Difference between revisions

Line 29:

=== Service developers ===

~~Services~~ could be:

Any developer could get benefits from 0install [http://0install.net/goals.html features] to:

* libraries or applications that are not intended to be included to ~~Sucrose~~

* provide libraries or applications that are not intended to be included to [[0.86/Sugar_Platform|Sugar Platform]]

** could be used by few activities

** have shorter or longer release/support schedules

** just a useful way to share your library w/o bundling binary blobs

* deploy dependencies that are specific to particular activity e.g. some python activities have C libraries, using Services, activity developer should not bundle all binaries that sugar supports but provide links to binaries that he managed to build and let Services build C libraries from sources on user side in the rest of cases

* dependencies that are specific to particular activity e.g. some python activities have C libraries, using Services, activity developer should not bundle all binaries that sugar supports but provide links to binaries that he managed to build and let Services build C libraries from sources on user side in the rest of cases

~~To create new service, developer needs to~~ [[Activity Team/Documentation/Services/Service Developers Guide|~~create and share]] proper feed which could be used [[Activity Team/Documentation/Services/Activity~~ Developers Guide~~|by activity developers~~]].

See [[Activity Team/Documentation/Services/Service Developers Guide|Service Developers Guide]] to know how to create service.

=== Geeks ===

@@ Line 29: / Line 29: @@
 === Service developers ===
-Services could be:
+Any developer could get benefits from 0install [http://0install.net/goals.html features] to:
-* libraries or applications that are not intended to be included to Sucrose
+* provide libraries or applications that are not intended to be included to [[0.86/Sugar_Platform|Sugar Platform]]
 ** could be used by few activities
 ** have shorter or longer release/support schedules
-** just a useful way to share your library w/o bundling binary blobs
+* deploy dependencies that are specific to particular activity e.g. some python activities have C libraries, using Services, activity developer should not bundle all binaries that sugar supports but provide links to binaries that he managed to build and let Services build C libraries from sources on user side in the rest of cases
-* dependencies that are specific to particular activity e.g. some python activities have C libraries, using Services, activity developer should not bundle all binaries that sugar supports but provide links to binaries that he managed to build and let Services build C libraries from sources on user side in the rest of cases
-To create new service, developer needs to [[Activity Team/Documentation/Services/Service Developers Guide|create and share]] proper feed which could be used [[Activity Team/Documentation/Services/Activity Developers Guide|by activity developers]].
+See [[Activity Team/Documentation/Services/Service Developers Guide|Service Developers Guide]] to know how to create service.
 === Geeks ===