5,705
edits
Changes
Jump to navigation
Jump to search
Line 43:
Line 43: − − === Multiple components === − − The sweet distribution might be split into several tarballs that can be composed in different ways when the same sweet release contains several implementations with different tarballs compositions. Possible use cases: − − * To save storage space or bandwidth when some tarballs will contain any-arch data that are common for all platforms and another tarball will contain binaries for a particular platform. − * ''TODO''. − − Additional components need to be placed to different sections with the same options as ''[Component]'' has: − − [Component/<nowiki><name></nowiki>] − − == Pitfalls == − − === Devel packages === − − It is common practice in binary-based GNU/Linux distributions to use satellite devel packages to collect various build-time files like C headers or pkg-config files. In the 0install environment, this doesn't work, because every package is stored in a separate directory hierarchy, e.g., *.so symlinks, from devel package, will point to nothing, since all *.so.* files from the library package live in a separate directory. − − Keep all build-time files in the runtime package.
Platform Team/Guide/Sweets Packaging (view source)
Revision as of 09:49, 24 December 2010
, 09:49, 24 December 2010no edit summary
* ''?'' matches any single character, except directory separator
* ''?'' matches any single character, except directory separator
* ''**'' matches everything, including directory separator
* ''**'' matches everything, including directory separator