From f89c0b08e32aa85d4b1e97ae2ab867ad1c011074 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sun, 14 Apr 2024 22:17:40 +0200 Subject: Adding upstream version 0.1.27. Signed-off-by: Daniel Baumann --- GETTING-STARTED-WITH-dh-debputy.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'GETTING-STARTED-WITH-dh-debputy.md') diff --git a/GETTING-STARTED-WITH-dh-debputy.md b/GETTING-STARTED-WITH-dh-debputy.md index ac0b034..7b6796b 100644 --- a/GETTING-STARTED-WITH-dh-debputy.md +++ b/GETTING-STARTED-WITH-dh-debputy.md @@ -53,7 +53,7 @@ Note: More options may appear in the future. ## Step 2: Have `debputy` convert relevant `debhelper` files The `debputy` integration with `debhelper` removes (replaces) some debhelper tools, but does **not** -read their relevant config files. These should instead be converted in to the new format. +read their relevant config files. These should instead be converted in to the new format. You can have `debputy` convert these for you by using the following command: @@ -247,14 +247,14 @@ using complex rules for pruning or moving around files in a way that are not eas _This is section does **not** apply to the `dh-sequence-zz-debputy-rrr` integration mode._ -The `dh_installman` tool auto-detects the language for manpages via two different methods: +The `dh_installman` tool auto-detects the language for man pages via two different methods: 1) By path name (Does the installation path look like `man//man
/...`?) 2) By basename (Does the basename look like `foo..
`?) Both methods are used in order with first match being the method of choice. Unfortunately, the second method is prune to false-positives. Does `foo.pl.1` mean a Polish translation of `foo.1` or is it the -manpage for a Perl script called `foo.pl` (similar happens for other languages/file extensions). +man page for a Perl script called `foo.pl` (similar happens for other languages/file extensions). To avoid this issue, `debputy` uses 1) by default and only that. Option 2) can be chosen by setting `language: derive-from-basename` on the concrete installation rule. The problem is that the migration tool @@ -312,7 +312,7 @@ _Remember to merge your manifest with previous steps rather than replacing it!_ `debputy migrate-from-dh` will merge its changes into existing manifests and can safely be re-run after adding/writing this base manifest. -### Covert your overrides for `dh_installsystemd`, `dh_installinit` (if any) +### Convert your overrides for `dh_installsystemd`, `dh_installinit` (if any) If your package overrides any of the service related helpers, the following use-cases have a trivial known solution: -- cgit v1.2.3