Platform Team/Guide/Sweets Packaging: Difference between revisions

Revision as of 19: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.

@@ Line 6: / Line 6: @@
 === 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.
+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.