[
https://issues.apache.org/jira/browse/BIGTOP-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13920607#comment-13920607
]
Bruno Mahé commented on BIGTOP-1214:
------------------------------------
What problem are you trying to solve?
Note that sub-packages dependencies is needed and cannot go away.
Dependencies between different projects may or may not be needed. Ex:
bigtop-utils providing some java classpath magic starting a specific version
and forces a version dependance.
On the other hand, we do not want either to prevent minor upgrades. Ex: Apache
Zookeeper 3.4.1 vs 3.4.2.
So unless there is a very good reason to remove versionned dependencies, I
would rather keep them or refine them.
> Remove component version dependency for apache cross component
> ---------------------------------------------------------------
>
> Key: BIGTOP-1214
> URL: https://issues.apache.org/jira/browse/BIGTOP-1214
> Project: Bigtop
> Issue Type: Improvement
> Components: RPM
> Reporter: Guo Ruijing
>
> Bigtop is to build/package/test one distro including apache component with
> specific version. It cannot guarantee all component version combination can
> work so that cross component version dependency will confuse user.
> for example:
> rpm -qp --requires hadoop-2.0.6-1.el6.x86_64.rpm
> bigtop-utils >= 0.7
> zookeeper >= 3.4.0
> The above dependency means hadoop-2.0.6-1.el6.x86_64.rpm can work with
> zookeeper 3.4.1, 3.4.2, 3.4.x. in fact, bigtop cannot support it so that
> bigtop may remove all cross component version dependency like:
> rpm -qp --requires hadoop-2.0.6-1.el6.x86_64.rpm
> bigtop-utils
> zookeeper
> for internal compoent, bigtop can keep existing dependency as:
> rpm -qp --requires hadoop-yarn-proxyserver-2.0.6-1.el6.x86_64.rpm
> hadoop-yarn = 2.0.6-1.el6 (expected)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
