Currently rpms are handled by downstream projects like Apache BigTop as
well as commercial distributions. So in my view it's a duplication of
efforts there, particularly since BigTop and distributions based on it also
harmonize dependencies to a certain extent and we mark many of our
dependencies as "provided".
So it's possible but not sure it's worth the effort since Flume depends on
so many other projects like Hadoop, HBase, etc
On Fri, Oct 14, 2016 at 9:36 AM, Lior Zeno <liorz...@gmail.com> wrote:
> Hi All,
> Currently, we distribute Flume via a tarball. I think we should improve and
> also publish deb and rpm packages that allow running Flume as a service.
> More over, container technology, such as Docker, has become increasingly
> popular in last few years. Publishing an official Docker image will allow
> easier deployment of Flume in the cloud.
> How do you guys feel about this?