Your message dated Wed, 6 Feb 2019 10:21:56 +0000
with message-id <20190206102156.cccyz76kvq3dm...@layer-acht.org>
and subject line re: please provide more information on multi-binary packages
has caused the Debian Bug report #216210,
regarding please provide more information on multi-binary packages
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
216210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=216210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: packaging-manual
Version: 3.2.1.0
Please provide documentation on multi-binary packages also in the debian
packaging manual. I have seen nowhere any documentation on how to do
multi-binary packages, and the solution to get a working multi-binary package
and look at it is not the best of solution.
The current situation only makes thing difficult for maintainer wanting to do
multi-binaries.
Friendly,
Sven Luther
--- End Message ---
--- Begin Message ---
Hi,
in 2008 the severity of this bug was changed, before that the last
change was in 2003. And in 2007 these changes were added to dev-ref
which is why I'm closing this bug now:
<section id="multiple-binary">
<title>Multiple binary packages</title>
<para>
A single source package will often build several binary packages, either to
provide several flavors of the same software (e.g., the <systemitem
role="package">vim</systemitem> source package) or to make several small
packages instead of a big one (e.g., so the user can install only the subset
needed, and thus save some disk space).
</para>
<para>
The second case can be easily managed in <filename>debian/rules</filename>.
You just need to move the appropriate files from the build directory into the
package's temporary trees. You can do this using <command>install</command> or
<command>dh_install</command> from <systemitem
role="package">debhelper</systemitem>. Be sure to check the different
permutations of the various packages, ensuring that you have the inter-package
dependencies set right in <filename>debian/control</filename>.
</para>
<para>
The first case is a bit more difficult since it involves multiple recompiles of
the same software but with different configuration options. The <systemitem
role="package">vim</systemitem> source package is an example of how to manage
this using a hand-crafted <filename>debian/rules</filename> file.
</para>
<!-- FIXME: Find a good debhelper example with multiple configure/make
cycles -->
</section>
It's definitly not perfect, also that FIXME should be fixed, but for now I think
it's good enough and thus I'm closing this bug report, so it doesnt clutter the
view of more urgent bugs to be fixed.
Also, we should really document dh9 style debian/rules in dev-ref...
--
tschüß,
Holger
-------------------------------------------------------------------------------
holger@(debian|reproducible-builds|layer-acht).org
PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C
signature.asc
Description: PGP signature
--- End Message ---
