Difference between revisions of "Platform Team/Guide/Sweets Packaging"
< Platform Team | Guide
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
=== Devel packages === | === 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 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., *.so symlinks, from devel package, will point to nothing since all *.so.* files from library package live in separate directory. |
| − | Keep all build time files in runtime package. | + | Keep all build time files in runtime package. |
Revision as of 20:27, 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., *.so symlinks, from devel package, will point to nothing since all *.so.* files from library package live in separate directory.
Keep all build time files in runtime package.