Platform Team/Guide/Sweets Packaging: Difference between revisions
| Line 177: | Line 177: | ||
Checking out will register a ''sweet'' in the local ''Sweets'' instance as a single ''implementation'' for the ''interfaces'' it ''implements''. This feature is especially useful for libraries, for example, if the sugar-toolkit sources, which implement the {{Code|sdk/sugar-toolkit}} ''interface'', were cloned to the {{Code|~/src/sugar-toolkit}} directory, then, while running a {{Code|sdk/sugar}} ''sweet'', it would become possible to reuse local sugar-toolkit sources as a regular ''implementation'' of the {{Code|sdk/sugar-toolkit}} dependency of {{Code|sdk/sugar}}. | Checking out will register a ''sweet'' in the local ''Sweets'' instance as a single ''implementation'' for the ''interfaces'' it ''implements''. This feature is especially useful for libraries, for example, if the sugar-toolkit sources, which implement the {{Code|sdk/sugar-toolkit}} ''interface'', were cloned to the {{Code|~/src/sugar-toolkit}} directory, then, while running a {{Code|sdk/sugar}} ''sweet'', it would become possible to reuse local sugar-toolkit sources as a regular ''implementation'' of the {{Code|sdk/sugar-toolkit}} dependency of {{Code|sdk/sugar}}. | ||
=== Sugar sweets === | |||
There are [[Platform_Team/Guide/Sweets_Usage#Sugar_via_Sweets|sdk/sugar]] sweets that might be used as an example how to support sweets. Sweets Sugar sources are [http://git.sugarlabs.org/sdk forks] of upstream projects with adding {{Code|sweets.recipe}} files and lightweight patches that make original code useful via Sweets. | |||
Checkout sources from: | |||
* http://git.sugarlabs.org/sdk/sugar-base | |||
* http://git.sugarlabs.org/sdk/sugar-toolkit | |||
* http://git.sugarlabs.org/sdk/sugar-artwork | |||
* http://git.sugarlabs.org/sdk/sugar | |||
and see its {{Code|sweets.recipe}} files. | |||
== Pitfalls == | == Pitfalls == | ||