5,705
edits
Changes
Jump to navigation
Jump to search
Line 63:
Line 63: − + Line 77:
Line 77: − Being a recipe, the package section cannot contain files-related options (since package itself does not contain any tarballs directly, only via recipe components), these options could be set only in components:+ − − * langs − * arch − * include − * exclude − * exec − * slots
Platform Team/Guide/Sweets Packaging (view source)
Revision as of 04:35, 30 July 2010
, 04:35, 30 July 2010→Recipes
The key differences between recipes and sub packages:
The key differences between recipes and sub packages:
* Sub packages are logically independent parts of the package;
* Sub packages are logically independent parts of the package, recipes make sense only to save storage space;
* Each sub package is identified by unique 0install url, all recipe components are identified by recipe url;
* Each sub package is identified by unique 0install url, all recipe components are identified by recipe url;
* Tarballs for different sub packages will be extracted to different directories, recipe component tarballs, within the same recipe, will be extracted to the same directory.
* Tarballs for different sub packages will be extracted to different directories, recipe component tarballs, within the same recipe, will be extracted to the same directory.
...
...
Recipe component sections can contain only files related options such as ''include'', ''exclude'', ''arch'' and ''langs''.
The same component could be a part of different recipes. In that case, different package implementations will contain the same recipe component tarball.
The same component could be a part of different recipes. In that case, different package implementations will contain the same recipe component tarball.