lumberjack package name does not coexist nicely along-side logstash-forwader

[wjimenez5271]

Discovered an unfortunate situation when trying to use lumberjack alongside logstash-forwarder (Elasticsearch's newest rev). Because the LSF proper package specifies that it obsoletes lumberjack, when you try to install the RPM for lumberjack it ignores that and installs logstash-forwarder instead.

Why is this a problem you might ask? Would you ever be using both? Well yes and no. Likely not on the same host, but perhaps in the same env that shares a YUM repo, especially when you are trying out lumberjack on a few select hosts but already have logstash-forwarder everywhere else.

My suggestion (and there are a number of ways to solve this), would be to rename the package to something like et-lumberjack (or maybe paulbunyan), to simply get away from any of the namespaces LSF uses. You could also of course rename it to logstash-forwarder but that brings with it other trade-offs in this regard.

Thanks for making some cools stuff, and keep up the good work!

-William

[jlintz]

My only personal greedy reason would be to vote for renaming to logstash-forwarder mainly so I don't have to redo the puppet module that makes references everywhere using that name( i know i'm lazy) , one of the reasons I haven't deployed this fork yet

[wjimenez5271]

@jlintz I think thats a perfectly acceptable justification, we don't get points for busy work ;-)