Difference between revisions of "Platform Team/Guide/Sweets Packaging"
| Line 7: | Line 7: | ||
The purpose of this HOWTO is describe how to get benefits of [[Activity_Team/Services|Sugar Services]] for your library/application, simplify support fork flows and let your users(developers) [[Activity_Team/Documentation/Services/Activity_Developers_HOWTO|use]] your code in simple and convenient way. | The purpose of this HOWTO is describe how to get benefits of [[Activity_Team/Services|Sugar Services]] for your library/application, simplify support fork flows and let your users(developers) [[Activity_Team/Documentation/Services/Activity_Developers_HOWTO|use]] your code in simple and convenient way. | ||
| − | + | Services are just a set of definitions for 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 publishing work flow is similar to activities. There is an info file, here ''service/service.info'', which describes current status(not history) of development process. All these fields, finally, go to feed file while publishing new version. | ||
| + | |||
| + | All fields should be placed to ''[Service]'' section | ||
| − | To start, install ''0sugar-publish'' which is main tool to maintain services infrastructure | + | * name |
| + | * summary | ||
| + | * description | ||
| + | * homepage | ||
| + | * version | ||
| + | * stability | ||
| + | * license | ||
| + | * binding | ||
| + | * main | ||
| + | * gpg-key | ||
| + | |||
| + | == 0sugar-publish tool == | ||
| + | |||
| + | To start using services, install ''0sugar-publish'' which is main tool to maintain services infrastructure. | ||
0alias 0sugar-publish http://download.sugarlabs.org/services/0sugar-publish/feed.xml | 0alias 0sugar-publish http://download.sugarlabs.org/services/0sugar-publish/feed.xml | ||
| − | |||
| − | |||
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.
Services are just a set of definitions for 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.
service.info file
Service publishing work flow is similar to activities. There is an info file, here service/service.info, which describes current status(not history) of development process. All these fields, finally, go to feed file while publishing new version.
All fields should be placed to [Service] section
- name
- summary
- description
- homepage
- version
- stability
- license
- binding
- main
- gpg-key
0sugar-publish tool
To start using services, install 0sugar-publish which is main tool to maintain services infrastructure.
0alias 0sugar-publish http://download.sugarlabs.org/services/0sugar-publish/feed.xml