[
https://issues.apache.org/jira/browse/BIGTOP-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13920648#comment-13920648
]
Bruno Mahé commented on BIGTOP-1214:
------------------------------------
In the current state, we do assume projects respects standard version schemas
and will not add completely new features in bug fixes.
So rather than having all dependencies go away, which project in particular is
not respecting bug-fix conventions in its releases?
For which projects in particular do you see not having any version dependency
being useful?
> 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)
