| DH_GNUSTEP(1) | User Contributed Perl Documentation | DH_GNUSTEP(1) |
dh_gnustep - perform various actions for GNUstep packages
dh_gnustep [debhelper options] [--app] [--appsupport] [--bundle] [--bundle-dir=directory] [--bug-script] [--game] [--move-to=package] [--no-cleanup] [--no-move]
dh_gnustep is a program based on debhelper(7) that is responsible for doing GNUstep-specific modifications, such as moving files in the GNUstep hierarchy to Filesystem Hierarchy Standard (FHS)-compliant locations. It also adds bug-script symlinks for GNUstep applications, removes some build system artifacts and adds additional dependendcies to packages that need it.
For brevity and because the GNUstep directories discussed are fairly long and cause readability issues when this manpage is being displayed on a typical terminal, the standard GNUstep variables are used as placeholders as follows:
GNUSTEP_SYSTEM_LIBRARY
/usr/lib/${DEB_HOST_MULTIARCH}/GNUstep
GNUSTEP_SYSTEM_HEADERS
/usr/include/${DEB_HOST_MULTIARCH}/GNUstep
GNUSTEP_SYSTEM_APPS
/usr/lib/${DEB_HOST_MULTIARCH}/GNUstep/Applications
GNUSTEP_SYSTEM_APPLICATION_SUPPORT
/usr/lib/${DEB_HOST_MULTIARCH}/GNUstep/ApplicationSupport
GNUSTEP_SYSTEM_BUNDLES
/usr/lib/${DEB_HOST_MULTIARCH}/GNUstep/Bundles
dh_gnustep must be run after dh_bugfiles(1) but before dh_link(1). Normally you would use an "override_dh_link" target but you should remember to invoke dh_link(1) as the last command in the recipe. This is mandatory so that the created links are made policy-compliant. Using the "execute_before_dh_link" target avoids this extra step. This program makes the following changes (all move operations can be cancelled with the --no-move option):
Note that dh_gnustep will not handle any other bug files and it expects dh_bugfiles(1) to have completed its job in order to handle the case when the bug-script symlink must be installed as /usr/share/bug/package/script (when there are bug-control or bug-presubj files). If an existing bug script is detected, dh_gnustep will emit a warning as a package can have only one bug-script file. In such situations the only solution is to integrate the contents of /usr/share/bug/gnustep-back-common into the existing script.
dh_gnustep accepts the common debhelper(7) options, and some specific ones. If you use any of the options below, make sure to build-depend on gnustep-make (>= 2.9.2-2) if that version is not already satisfied in the current stable/oldstable release. Some options are implemented in subsequent releases, as documented below.
Care shhould be taken when using this option because some apps contain architecture-dependent files in their resource bundle. Another important point to pay attention to: if this is an existing package which does not have its resources moved to /usr/share, a maintscript is required because dpkg will not switch a directory to a symlink (and vice-versa). dh_gnustep does not handle this, see dpkg-maintscript-helper(1).
This option is incompatible with --no-move and for multi-binary packages sometimes should be used with the appropriate -p option.
Note that bundles' resources sometimes contain architecture-dependent files in which case the best approach is to move the architecture-independent files manually.
This option was introduced in gnustep-make/2.9.2-3 and like --app it is incompatible with --no-move.
This option was introduced in gnustep-make/2.9.2-4 and it is incompatible with --no-move. Furthermore, --bundle and --bundle-dir are mutually exclusive. If the package installs bundles in the standard Bundles directory and in another non-standard directory, you'll have to run dh_gnustep twice with different arguments if you need to move all of the resource bundles.
If --app, --appsupport and --bundle are used together, all resource bundles are moved to the package specified by the option's argument, there is no way to split them in different packages. The current implementation will handle more than one app per binary package but it will fail with a multi-binary source package containing more than one ".app" binary package. Likewise, if the package contains more than one ApplicationSupport directory, they will be processed independently as expected but the build is likely to fail if they are in different binary packages.
Use with caution; see the EXAMPLES section for working examples.
execute_before_dh_link:
dh_gnustep -pgnustep-dl2 --no-move --bug-script
dh_gnustep --remaining-packages
Do not move any files for the gnustep-dl2 package (as that's already handled manually) but install a bug-script symlink because the package contains an application and a Gorm palette.
execute_before_dh_link:
dh_gnustep --app --move-to=lynkeos.app-common
Move the lynkeos.app resource bundle to the architecture-independent package lynkeos.app-common.
override_dh_link:
dh_gnustep --app --game
dh_link
Move the app's resource bundle to /usr/share and the symlink to the executable from /usr/bin to /user/games. Additionally, assuming the binary package name ends with ".app", create a bug-script symlink pointing to /usr/share/bug/gnustep-back-common. Finally, delete the stamp.make file from the app bundle.
execute_before_dh_link:
ifneq (,$(filter gnustep-gui-runtime,$(shell dh_listpackages)))
dh_gnustep -pgnustep-gui-runtime --app \
--bundle-dir=ColorPickers --move-to=gnustep-gui-common
dh_gnustep --remaining-packages
else
dh_gnustep --app --bundle-dir=ColorPickers \
--move-to=gnustep-gui-common
endif
Move the resource bundles of two apps and the resources of all ColorPickers' bundles to /usr/share in the gnustep-gui-common package. Note that dh_gnustep will automatically figure out that the package they are being moved from is gnustep-gui-runtime and there is no need to use debhelper's -p option. The conditional is only necessary to support full builds so that the symlinks are created in the gnustep-gui-runtime package.
Should implement -X option.
Should do something with Java classes -- make a jar file and move from Library/Libraries/Java to /usr/share/java -- to comply with Java policy.
Debian Policy, version 4.7.0
FHS, version 3.0
Multiarch specification, <https://wiki.ubuntu.com/MultiarchSpec>
debhelper(7), dh_link(1), dh_bugfiles(1)
This program is not part of debhelper.
Hubert Chan <uhoreg@debian.org>
Yavor Doganov <yavor@gnu.org>
| 2025-03-05 | perl v5.40.1 |