summaryrefslogtreecommitdiffstats
path: root/GETTING-STARTED-WITH-dh-debputy.md
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--GETTING-STARTED-WITH-dh-debputy.md5
1 files changed, 4 insertions, 1 deletions
diff --git a/GETTING-STARTED-WITH-dh-debputy.md b/GETTING-STARTED-WITH-dh-debputy.md
index d14e6e4..227f6d7 100644
--- a/GETTING-STARTED-WITH-dh-debputy.md
+++ b/GETTING-STARTED-WITH-dh-debputy.md
@@ -134,13 +134,16 @@ The following `debhelper` commands are replaced in the `dh-sequence-zz-debputy-r
`debputy migrate-from-dh` will warn you if there is anything to worry about in relation to these commands.
* `dh_fixperms`
+ * `dh_shlibdeps`
* `dh_gencontrol`
* `dh_md5sums`
* `dh_builddeb`
In case something is flagged, it is most likely a hook target, which either have to be converted to `debputy`'s
features or moved earlier. The most common cases are hook targets for `dh_fixperms` and `dh_gencontrol`, which
-have sections below advising how to approach those.
+have sections below advising how to approach those. The only potential problematic command would be `dh_shlibdeps`.
+The `debputy` toolchain replaces `dh_shlibdeps` with a similar behavior to that of debhelper compat 14. If
+you need selective promotion or demotion of parts of a substvar, then that is currently not supported.
### Affected debhelper command list for `dh-sequence-zz-debputy` integration mode