Platform Team/Guide/Sweets Packaging

This guide describes how to use Sugar Labs' Packaging Management System to distribute software projects. See also the 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 the development 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 an activity/activity.info file (that conforms to the same spec) for activities. All sweets for Glucose components are located in the http://git.sugarlabs.org/sdk project.

Once 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 install 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 location, 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).