On 08/08/2012 06:30 PM, Ewan Mellor wrote:
We need to push this discussion on build systems to a conclusion. Let me
summarize so far.
* We need to be able to build CloudStack in various configurations (support for
the range of hypervisors turned on or off, etc).
Yes
* We would like the build tool to be able to get the necessary dependencies
automatically, to avoid the user having to download a dozen libraries from all
sorts of different places.
Not necessarily. This cannot be a "hard coded" "feature" of the build
tool. For package build systems used by distributions network access is
often not available, thus automatic download of dependencies will fail.
Whatever tool is chosen must be able to handle the "do not download
anything" case.
* Many of our dependencies are version-dependent, so we would want to get a
specific version or at the very least have greater-than constraints on the
version that is downloaded.
* We want to be able to package CloudStack in RPMs and .debs that correctly
depend on packages available on the target platform.
This is IMHO not a "job" of the project. This is up to the packagers and
package maintainers for the various distros. I will maintain openSUSE
and SLE builds in OBS and would very much prefer that the build system
know nothing about how to build an rpm. We should maintain a "reference
spec file" in the source tree and I will contribute to that, but having
the build system crank out a .deb or .rpm package is just not the best
approach.
My $0.02
Robert
--
Robert Schweikert MAY THE SOURCE BE WITH YOU
SUSE-IBM Software Integration Center LINUX
Tech Lead
rjsch...@suse.com
rschw...@ca.ibm.com
781-464-8147
