Difference between revisions of "Platform Team/Guide/Sweets Packaging"
m |
|||
| Line 1: | Line 1: | ||
| − | {{ | + | This guide describes how to use Sugar Labs' Packaging Management System to distribute software projects. See also [[Platform_Team/Sweets|introduction page]] and [[Platform_Team/Guide/Sweets_Usage|Usage guide]]. |
| + | |||
| + | == Development workflow with sweets == | ||
| + | |||
| + | During the first launch, sources will be auto-built and kept in internal storage. To make sweets useful for development, checkout developing project sources in sweets: | ||
| + | |||
| + | sweets checkout [''path-to-sources''] | ||
| + | |||
| + | The only thing that is required from sources is having a [[Platform Team/Recipe Specification|sweets.recipe]] spec file for non-activity projects or {{Code|activity/activity.info}} (that conforms to the same spec) for activities. All sweets for Glucose components are located in the http://git.sugarlabs.org/sdk project. | ||
| + | |||
| + | After being checked out, these sources might be launched using {{Code|<nowiki>http://</nowiki>sweets.sugarlabs.org/''sweet-value-from-sweets.recipe''}} or just mentioning a sweet value: | ||
| + | |||
| + | sweets ''sweet'' | ||
| + | |||
| + | For glucose projects, you can find ready-to-use and always-rebased-to-upstream projects in the [http://git.sugarlabs.org/sdk SDK] http://git.sugarlabs.org project. For now, there are two branches: {{Code|master}} for recent trunk, and {{Code|master-0.88}} for 0.88 code based on Dextrose-2 patches. | ||
| + | |||
| + | Checked out projects will be built according to the {{Code|[Build]}} section commands in the {{Code|sweets.recipe}} files. In general, for autotools-based projects, there is no further need for the {{Code|sweets}} command, just run {{Code|make install}} to build current sources and {{Code|make install them}} them to the directory that was specified by {{Code|sweets}} in the configure stage. For glucose projects, there is no need even in calling the {{Code|make}} command (python code will be reused from its original place, see {{Code|binding}} options in [[Platform Team/Recipe Specification|sweets.recipe]] files), just change the code and restart sugar. | ||
| + | |||
| + | == Feedback == | ||
| + | |||
| + | * [http://bugs.sugarlabs.org/newticket?component=sweets Submit] your bug report. | ||
| + | * Ask your question on IRC channels, [irc://irc.freenode.net/sugar #sugar] (not logged) or [irc://irc.freenode.net/sugar-newbies #sugar-newbies] (logged). | ||
| + | |||
| + | <!-- | ||
== Writing recipe files == | == Writing recipe files == | ||
| Line 52: | Line 75: | ||
Keep all build-time files in the runtime package. | Keep all build-time files in the runtime package. | ||
| − | + | ||
| + | |||
| + | |||
| + | |||
== Introduction == | == Introduction == | ||
Revision as of 11:03, 9 September 2011
This guide describes how to use Sugar Labs' Packaging Management System to distribute software projects. See also introduction page and Usage guide.
Development workflow with sweets
During the first launch, sources will be auto-built and kept in internal storage. To make sweets useful for development, checkout developing project sources in sweets:
sweets checkout [path-to-sources]
The only thing that is required from sources is having a sweets.recipe spec file for non-activity projects or activity/activity.info (that conforms to the same spec) for activities. All sweets for Glucose components are located in the http://git.sugarlabs.org/sdk project.
After being checked out, these sources might be launched using http://sweets.sugarlabs.org/sweet-value-from-sweets.recipe or just mentioning a sweet value:
sweets sweet
For glucose projects, you can find ready-to-use and always-rebased-to-upstream projects in the SDK http://git.sugarlabs.org project. For now, there are two branches: master for recent trunk, and master-0.88 for 0.88 code based on Dextrose-2 patches.
Checked out projects will be built according to the [Build] section commands in the sweets.recipe files. In general, for autotools-based projects, there is no further need for the sweets command, just run make install to build current sources and make install them them to the directory that was specified by sweets in the configure stage. For glucose projects, there is no need even in calling the make command (python code will be reused from its original place, see binding options in sweets.recipe files), just change the code and restart sugar.
Feedback
- Submit your bug report.
- Ask your question on IRC channels, #sugar (not logged) or #sugar-newbies (logged).