Bug#758611: include all modules?

[Emmanuel Bourg]

Le 19/08/2014 10:44, Daniel Pocock a écrit :

> What exactly does this mean - is it about what should be built or what
> should be included in the binary package?

I agree this message is unclear. 'yes' means the package will be
configured to build all modules, 'no' means mh_make will then ask what
modules should be built. It doesn't affect which modules will be installed.


> For my own package, some of the modules need to be built and used at
> build time but they do not need to be included in the binary package
> that is produced.  Should I say yes or no for such modules?

Any module built is automatically installed. It isn't possible to build
a module and not install it. This is indeed annoying when some modules
are only useful for the tests and end up being installed in the final
package. This increases the size of the package and adds useless
dependencies (this can be seen with the wagon2 package for example where
the wagon-tck-http module is installed).

Emmanuel Bourg

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#758611: include all modules?

[Daniel Pocock]

Package: maven-debian-helper


When running mh_make I see the prompt:

This project contains modules. Include all modules?
[y]/n 


What exactly does this mean - is it about what should be built or what
should be included in the binary package?

For my own package, some of the modules need to be built and used at
build time but they do not need to be included in the binary package
that is produced.  Should I say yes or no for such modules?

__
This is the maintainer address of Debian's Java team
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. 
Please use
debian-j...@lists.debian.org for discussions and questions.