Difference between revisions of "Platform Team/Guide/Sweets Packaging"
< Platform Team | Guide
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
== How it works == | == How it works == | ||
| + | |||
| + | Services are just a set of predefined urls and names for 0install feeds, it provides to activity developers [[Activity_Team/Documentation/Services/Activity_Developers_HOWTO#Using_Services|convenient]] way to use services. But [http://0install.net/injector-packagers.html regular 0install work flow] still [[Activity_Team/Documentation/Services/Activity_Developers_HOWTO#Low_level_using_of_0install_feeds|works]]. The rest of document describes sugar specific work flow to meet [[Activity_Team/Documentation/Services/Activity_Developers_HOWTO#Using_Services|0sugar]] benefits. | ||
== service.info file == | == service.info file == | ||
Revision as of 12:25, 19 December 2009
Introduction
The purpose of this HOWTO is describe how to get benefits of Sugar Services for your library/application, simplify support fork flows and let your users(developers) use your code in simple and convenient way.
How it works
Services are just a set of predefined urls and names for 0install feeds, it provides to activity developers convenient way to use services. But regular 0install work flow still works. The rest of document describes sugar specific work flow to meet 0sugar benefits.