Platform Team/Guide/Sweets Packaging: Difference between revisions
| Line 217: | Line 217: | ||
=== Developing activities === | === Developing activities === | ||
The regular way for development related routines regarding activity sources is runing {{Code|setup.py}} script located in the root activity directory. With Sweets, all | The regular way for development related routines regarding activity sources is runing {{Code|setup.py}} script located in the root activity directory. With Sweets, all these routines might be used with {{Code|sweets}} command. The reasons are: | ||
* The downside of using Sweets is that running {{Code|setup.py}} requires being in the Sugar session (to have all libraries that {{Code|setup.py}} injected); | * The downside of using Sweets is that running {{Code|setup.py}} requires being in the Sugar session (to have all libraries that {{Code|setup.py}} injected); | ||
* Sweets is designed to support multiple software versions at the same time, it | * Sweets is designed to support multiple software versions at the same time, it is not useful to login to different Sugar session for creating, e.g., source tarballs; In other words, having standalone utility makes more sense; | ||
* {{Code|sweets}} command already contains development related functionality, it is useful to keep all development related functions in one utility. | * {{Code|sweets}} command already contains development related functionality, it is useful to keep all development related functions in one utility. | ||