Bug 114074 - ccm-tools need to depend on ccm-config-libs >= 1.2
ccm-tools need to depend on ccm-config-libs >= 1.2
Product: Red Hat Web Application Framework
Classification: Retired
Component: installation (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Dennis Gregorovic
Jon Orris
Depends On:
Blocks: 106481
  Show dependency treegraph
Reported: 2004-01-22 05:53 EST by Matthew Booth
Modified: 2007-04-18 13:01 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-01-27 16:43:34 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Matthew Booth 2004-01-22 05:53:10 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030922

Description of problem:
ccm-tools has a dependency on ccm-config-libs, which means it will
install without warnings on a machine with ccm-config-libs-1.1.x
installed. However it will not work.

Upgrading to ccm-config-libs-1.2.x will fix the problems, so the
dependency should either be on ccm-config-libs >= 1.2 or on individual
files in ccm-config-libs.

Version-Release number of selected component (if applicable):
ccm-tools-0.9.0-2 (from tip of dev @39491)

Additional info:
Comment 1 Dennis Gregorovic 2004-01-23 14:21:30 EST
Actually, ccm-tools does not have any dependency on ccm-config-libs. 
This is correct because ccm-tools itself does not require anything in
ccm-config-libs.  The package that should depend on ccm-config-libs is

As of @39642, the buildRequires elements of application.xml are used
to generate BuildRequires tags in the RPM.  This means that the latest
ccm-core source RPMs require junit, httpunit, junitperf, and servlet.  

However, we still have the problem that ccm-core binary RPMs should
also depend on servlet.  Here are some solutions to this that I can
think of offhand:

1) add another type of dependency tag to application.xml that will
cause a dependency to be generated in the RPM, but won't be treated as
 a ccm application.  Example: <ccm:runRequires name="servlet"

2) add "Requires: servlet = 2.3" to rpm.spec.in.  However, this isn't
very forward-compatible.

3) create a one-off rpm spec file for core.  This could be a lot of
maintainence work.

4) have ccm-tools RPM depend on servlet 2.3.  Same downside as #2

So, my preference would be #1.  Thoughts?
Comment 2 Daniel Berrange 2004-01-27 09:36:44 EST
Yeah, I think #1 is best.
Comment 3 Dennis Gregorovic 2004-01-27 10:20:55 EST
@ 39788 

Note You need to log in before you can comment on or make changes to this bug.