Difference between revisions of "Platform Team/Guide/Sweets Packaging"
< Platform Team | Guide
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
{{TOCright}} | {{TOCright}} | ||
[[Category:Services/Documentation]] | [[Category:Services/Documentation]] | ||
| − | < | + | |
| + | == 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 of pkg-config files. In 0install environment, it doesn't work because every package is stored in separate directory hierarchy, e.g., if *.so symlinks, from devel package, will point to nothing because all *.so.* files from library package live in separate directory. | ||
| + | |||
| + | Keep all build time files in runtime package. | ||
| + | |||
| + | |||
| + | <!-- | ||
== Introduction == | == Introduction == | ||
| Line 104: | Line 111: | ||
* [http://0install.net/interface-spec.html Feed file format specification] | * [http://0install.net/interface-spec.html Feed file format specification] | ||
* [http://0install.net/0compile.html 0compile] [http://0install.net/0compile-dev.html guide] | * [http://0install.net/0compile.html 0compile] [http://0install.net/0compile-dev.html guide] | ||
| + | --> | ||
Revision as of 19:25, 20 July 2010
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 of pkg-config files. In 0install environment, it doesn't work because every package is stored in separate directory hierarchy, e.g., if *.so symlinks, from devel package, will point to nothing because all *.so.* files from library package live in separate directory.
Keep all build time files in runtime package.