-msgid ""
-"If your source package generates more than one binary package, debhelper "
-"programs will default to acting on all binary packages when run. If your "
-"source package happens to generate one architecture dependent package, and "
-"another architecture independent package, this is not the correct behavior, "
-"because you need to generate the architecture dependent packages in the "
-"binary-arch debian/rules target, and the architecture independent packages "
-"in the binary-indep debian/rules target."
-msgstr ""
-
-#. type: textblock
-#: debhelper.pod:252
-msgid ""
-"To facilitate this, as well as give you more control over which packages are "
-"acted on by debhelper programs, all debhelper programs accept the B<-a>, "
-"B<-i>, B<-p>, and B<-s> parameters. These parameters are cumulative. If "
-"none are given, debhelper programs default to acting on all packages listed "
-"in the control file."
-msgstr ""
-
-#. type: =head2
-#: debhelper.pod:258
-msgid "Automatic generation of debian install scripts"
-msgstr ""
-
-#. type: textblock
-#: debhelper.pod:260
-msgid ""
-"Some debhelper commands will automatically generate parts of debian "
-"maintainer scripts. If you want these automatically generated things "
-"included in your existing debian maintainer scripts, then you need to add "
-"\"#DEBHELPER#\" to your scripts, in the place the code should be added. "
-"\"#DEBHELPER#\" will be replaced by any auto-generated code when you run "
-"dh_installdeb."
-msgstr ""
-
-#. type: textblock
-#: debhelper.pod:267
-msgid ""
-"If a script does not exist at all and debhelper needs to add something to "
-"it, then debhelper will create the complete script."
-msgstr ""
-
-#. type: textblock
-#: debhelper.pod:270
-msgid ""
-"All debhelper commands that automatically generate code in this way let it "
-"be disabled by the -n parameter (see above)."
-msgstr ""
-
-#. type: textblock
-#: debhelper.pod:273
-msgid ""
-"Note that the inserted code will be shell code, so you cannot directly use "
-"it in a perl script. If you would like to embed it into a perl script, here "
-"is one way to do that (note that I made sure that $1, $2, etc are set with "
-"the set command):"
-msgstr ""
-
-#. type: verbatim
-#: debhelper.pod:278
-#, no-wrap
-msgid ""
-" my $temp=\"set -e\\nset -- @ARGV\\n\" . << 'EOF';\n"
-" #DEBHELPER#\n"
-" EOF\n"
-" system ($temp) / 256 == 0\n"
-" \tor die \"Problem with debhelper scripts: $!\";\n"
-"\n"
-msgstr ""
-
-#. type: =head2
-#: debhelper.pod:284
-msgid "Automatic generation of miscellaneous dependencies."
-msgstr ""
-
-#. type: textblock
-#: debhelper.pod:286
-msgid ""
-"Some debhelper commands may make the generated package need to depend on "
-"some other packages. For example, if you use L<dh_installdebconf(1)>, your "
-"package will generally need to depend on debconf. Or if you use "
-"L<dh_installxfonts(1)>, your package will generally need to depend on a "
-"particular version of xutils. Keeping track of these miscellaneous "
-"dependencies can be annoying since they are dependant on how debhelper does "
-"things, so debhelper offers a way to automate it."
-msgstr ""
-
-#. type: textblock
-#: debhelper.pod:294
-msgid ""
-"All commands of this type, besides documenting what dependencies may be "
-"needed on their man pages, will automatically generate a substvar called "
-"${misc:Depends}. If you put that token into your debian/control file, it "
-"will be expanded to the dependencies debhelper figures you need."