https://bugzilla.redhat.com/show_bug.cgi?id=1226445
--- Comment #3 from david(a)algorithmicarmada.com ---
Probably the easiest option is renaming bin/plugin slightly to be more uniquely
named, then sticking it in the usual bin folder.
Based on what I'm seeing in 7-zip, the official RPM[1][2] simply sticks
"plugin" in /usr/share/bin/ and creates a folder for plugins in
/usr/share/elasticsearch/plugins.
It'd be nice to see packages for plugins, but that seems impractical due to the
community-driven nature of plugins. Plus, the documented experience is being
able to run the "plugin" binary.
I've filed issue #11651[3] with upstream github repo in hopes that upstream
will consider naming their script in a more useful manner.
--
[1]
https://download.elastic.co/elasticsearch/elasticsearch/elasticsearch-1.6...
[2]
https://github.com/elastic/elasticsearch/blob/master/core/src/packaging/r...
proves that the packaging process is part of the repo, and therefore under
Apache license. Sadly, mostly driven by maven.
[3]
https://github.com/elastic/elasticsearch/issues/11651
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug
https://bugzilla.redhat.com/token.cgi?t=dUrTfPprvi&a=cc_unsubscribe