Platform Team/Guide/Sweets Packaging: Difference between revisions
| Line 232: | Line 232: | ||
And don't support the following: | And don't support the following: | ||
* {{Code|dev}}, seems to be needlessly exaggerated, function creates symbolic link in {{Code|~/Activities}} directory to activity sources, the same might be done using {{Code|ln -s}} command to avoid having derived functionality; | * {{Code|dev}}, seems to be needlessly exaggerated, function creates symbolic link in {{Code|~/Activities}} directory to activity sources, the same might be done using {{Code|ln -s}} command to avoid having derived functionality, or better, place source exactly to {{Code|~/Activities}} directory; | ||
* {{Code|fix_manifest}}, function create {{Code|MANIFEST}} file, not having this file is not a fail and Sweets is designed to have include/exclude rules in recipe files instead; | * {{Code|fix_manifest}}, function create {{Code|MANIFEST}} file, not having this file is not a fail and Sweets is designed to have include/exclude rules in recipe files instead; | ||
* {{Code|install}}, function installs activity to the root system, Sweets avoid, by design, any global changes during the regular behaviour. | * {{Code|install}}, function installs activity to the root system, Sweets avoid, by design, any global changes during the regular behaviour. | ||