TABLE OF CONTENTS


Postinstall

[ Top ] [ Chapter 11 ] [ Concepts ]


Core X11 Fonts

[ Top ] [ Postinstall ] [ Postinstall Steps ]

DESCRIPTION

Font directories which are registered with a symlink in the X11 font catalogue (for use as server-side core fonts) will have the 'fonts.dir' and 'fonts.scale' files created automatically. Such packages require the 'mkfontdir' and 'mkfontscale' packages at build time.


Freedesktop.org MIME

[ Top ] [ Postinstall ] [ Postinstall Steps ]

DESCRIPTION

Packages which include desktop menu entries with MimeType declarations, or additional definitions for the Shared MIME-Info database, will be cleaned up from update-desktop-database or update-mime-database commands mistakenly run in $D. The desktop-file-utils and shared-mime-info packages include perpetual postinstall scripts which handle their respective database caches.


GConf Schemas

[ Top ] [ Postinstall ] [ Postinstall Steps ]

DESCRIPTION

Package postinstall and preremove scripts will be automatically generated to un/register GConf schemas into the system GConf database.

NOTE

Packages providing GConf schemas must require the GConf2 package.

SEE ALSO

RESTRICT


GdkPixbuf Loaders

[ Top ] [ Postinstall ] [ Postinstall Steps ]

DESCRIPTION

Package postinstall scripts will be automatically generated to register GdkPixbuf loaders with the system GdkPixbuf loader cache.

NOTE

Packages providing GdkPixbuf loaders will always require libgdk_pixbuf2.0_0.


GTK+ Input Method Modules

[ Top ] [ Postinstall ] [ Postinstall Steps ]

DESCRIPTION

Package postinstall scripts will be automatically generated to register GTK+ Input Method Modules with the system module cache.

NOTE

Packages providing GTK Input Method Modules will always require either libgtk2.0_0 or libgtk3_0, depending on which version of GTK+ it supports.


Icon Themes

[ Top ] [ Postinstall ] [ Postinstall Steps ]

DESCRIPTION

Perpetual postinstall scripts will be automatically generated for packages providing an icon theme, and postinstall triggers for those adding additional icons for a given theme to update that icon theme's cache.


Python Bytecompiling

[ Top ] [ Postinstall ] [ Postinstall Steps ]

DESCRIPTION

All Python modules installed into the system site-packages directories (/usr/lib/pythonX.Y) are automatically byte-compiled.


TeX Live

[ Top ] [ Postinstall ] [ Postinstall Steps ]

DESCRIPTION

Package postinstall and preremove scripts will be automatically generated for packages installing TeX files into the system TEXMF tree, which will update the ls-R databases, TeX font maps, and TeX format files.

NOTE

Packages providing TeX files must require the texlive-collection-basic package, and also the fontconfig package if OTF, TTF, or Type1 fonts are provided.


X Sessions

[ Top ] [ Postinstall ] [ Postinstall Steps ]

DESCRIPTION

Package postinstall and preremove scripts will be automatically generated for packages which provide X sessions to manage Start Menu shortcuts which will launch the session.

NOTE

Packages providing X sessions must require the cygutils, dbus-x11, run, and xinit packages.


Documentation Files

[ Top ] [ Postinstall ] [ Postinstall Steps ]

DESCRIPTION

Standard documentation files in $S will be automatically installed into $D/usr/share/doc/PN. Empty files will be skipped.

SEE ALSO

RESTRICT


DOCS

[ Top ] [ Documentation Files ] [ Variables ]

DESCRIPTION

A list of documentation files, relative to $S, to be installed. Note that most standard documentation files are installed automatically and do not need to specified here.


HTMLDOCS

[ Top ] [ Documentation Files ] [ Variables ]

DESCRIPTION

A list of HTML documentation files, relative to $S, to be installed in the html subdirectory of the standard docdir.


PKG_DOCS

[ Top ] [ Documentation Files ] [ Variables ]

DESCRIPTION

A list of documentation files, relative to $S, to be installed in a PKG-specific docdir and automatically included in the PKG subpackage. The PKG_DOCS name is descriptive rather than literal, where "PKG" should be substituted with the name of the binary package to whose contents the docs should be added. When a package contains a character which cannot be used in a shell variable name (namely '+', '-', and '.'), that character must be substituted with an underscore ('_'), e.g. libfoo_devel_DOCS for a libfoo-devel package.

NOTE

When using PKG_DOCS, usr/share/doc/PKG should not be included in the corresponding PKG_CONTENTS; the specified files will be added to the package automatically.


Emacs Lisp

[ Top ] [ Postinstall ] [ Postinstall Steps ]

DESCRIPTION

Emacs Lisp files will be automatically byte-compiled if emacs is present.


Man Pages

[ Top ] [ Postinstall ] [ Postinstall Steps ]

DESCRIPTION

The following cleanup steps will occur if man pages are installed:


Info Pages

[ Top ] [ Postinstall ] [ Postinstall Steps ]

DESCRIPTION

The following cleanup steps will occur if info pages are installed:

SEE ALSO

RESTRICT


Perl Modules

[ Top ] [ Postinstall ] [ Postinstall Steps ]

DESCRIPTION

The following cleanup steps will occur if Perl module(s) are installed:


Game Data

[ Top ] [ Postinstall ] [ Postinstall Steps ]

DESCRIPTION

Game data installed into /var/games will be handled with make_etc_defaults.


Empty Directories

[ Top ] [ Postinstall ] [ Postinstall Steps ]

DESCRIPTION

Empty directories will be removed automatically, unless marked for saving with keepdir or KEEPDIRS.


KEEPDIRS

[ Top ] [ Empty Directories ] [ Variables ]

SYNOPSIS

  KEEPDIRS="DIRECTORY [DIRECTORY...]"

DESCRIPTION

The equivalent of calling keepdir on the given directories. This variable can be used for convenience to avoid defining a custom src_install solely in order to add a keepdir command.


Strip Binaries

[ Top ] [ Postinstall ] [ Postinstall Steps ]

DESCRIPTION

Debug symbols in executables and shared libraries will be stripped automatically, except for executables containing bytecode which cannot be stripped.

SEE ALSO

RESTRICT


Split Debugging Information

[ Top ] [ Postinstall ] [ Postinstall Steps ]

DESCRIPTION

Debug symbols stripped from executables and libraries are preserved as split debuginfo files, and sources referenced therein are automatically installed into a package-specific location. A PN-debuginfo package will be automatically created with split debugging symbols and source files when present; inclusion in PKG_NAMES and PKG_CONTENTS is not necessary.

SEE ALSO

RESTRICT


Libtool Libraries

[ Top ] [ Postinstall ] [ Postinstall Steps ]

DESCRIPTION

Libtool libraries use .la ("libtool archive") files to represent the library in a cross-platform way during the build process. By default, these are installed alongside the library, in which they serve two possible purposes: to help lt_dlopen() (or sometimes g_module_open()) find the DLL, and to determine its dependencies when linking something else against it.

The following steps will occur automatically when libtool libraries are included in a package:


KEEP_LA_FILES

[ Top ] [ Libtool Libraries ] [ Variables ]

SYNOPSIS

  KEEP_LA_FILES=[all|module|shared|static|none]

DESCRIPTION

Most of the time, libtool library files are not truly necessary, in which case they end up just slowing down builds and sometimes even causing a module to be loaded twice. Therefore, many distributions have begun removing them from binary packages.

Whether and which .la files are removed during automatic postinstall is based on the value of this variable, which can be one of:

Some suggested guidelines:


RESTRICT

[ Top ] [ Postinstall ] [ Variables ]

DESCRIPTION

List of automatic postinstall or packaging step(s) which should be skipped for this package. Supported values are:

Of these, "diff" is the only one that should be considered useful, e.g. with very large data-only packages which will have no useful diff. "debuginfo" is useful on a temporary, per-build basis to debug a package in the build tree (e.g. a noinst test package). "upload" makes it safer for cygport to be used for building private packages.

If you find yourself using any of the others to work around cygport's default behaviour, in all likelyhood it is either a bug in cygport or in the .cygport file.