[
https://issues.apache.org/jira/browse/ZOOKEEPER-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179103#comment-15179103
]
Eric Yang commented on ZOOKEEPER-1604:
--------------------------------------
If ZOOKEEPER-2007 was committed, then ZOOKEEPER-2275 would not exist.
Evidently, There are people that are willing to provide patch for packaging
issues. Instead, ZOOKEEPER-2007 patch were left without review and code became
stale. (Code did not apply due to pre-commit test did not verify patch depth,
not the patch.) BigTop has some security issues, including non-uniform uid/gid
generation on cluster, and including security vulnerable packages. I am only
presenting facts for others to consider. It seems like it's a few steps
backward because BigTop project create interlocks of open source projects
instead of allow individual project to evolve on their own pace. Ex-Cloudera
developers had made some poor choices in BigTop project direction, rather than
allowing other projects to evolve. Granted that this is my opinion, and I
respect yours. Good luck with BigTop.
> remove rpm/deb/... packaging
> ----------------------------
>
> Key: ZOOKEEPER-1604
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1604
> Project: ZooKeeper
> Issue Type: Task
> Components: build
> Affects Versions: 3.3.0
> Reporter: Patrick Hunt
> Assignee: Chris Nauroth
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-1604.001.patch, ZOOKEEPER-1604.patch
>
>
> Remove rpm/deb/... packaging from our source repo. Now that BigTop is
> available and fully supporting ZK it's no longer necessary for us to attempt
> to include this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
