On Wed, 2010-11-10 at 18:03 +0000, Gordon Sim wrote: > ... > In my mind the ideal is that when creating a dist, the full source for > all possible modules are included regardless of whether the deps for > those are available at the time of creation. That way you ease the > burden of getting the system setup for creating the dist and leverage > the existing systems of a wider group of testers for checking all the > different parts. I think that is also less error prone because the > configuration of the system on which the dist is created doesn't > inadvertently cause important pieces to be missed. (e.g. at present we > include the cman integration sources regardless of whether cman is > installed when the dist is created).
I entirely agree with this. I think the confusion is that an Apache release by its definition is a _source_ release and so should include all the source not just the source that would build on the release manager's packaging machine. The problem is essentially because the C++ release process used to (and may still - I'm not sure) require a build of all executables that have man pages so that they can be run --help to feed the man page creation process. Becuase of this the autotools make dist target has got confusingly tangled up with the executable build process so that the configure conditionals apply to it. Andrew --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
