[
https://issues.apache.org/jira/browse/BIGTOP-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14081532#comment-14081532
]
Sean Mackrory commented on BIGTOP-1159:
---------------------------------------
{quote}But why shouldn't plugins be managed through packages as well? {quote}
Plugins that were delivered as packages would sidestep my concern entirely, so
if we foresee that being the main use for this directory, then you have a more
enthusiastic +1 from me. The /var/lib/bigtop thing was initially motivated by
plugins that were added manually by the user and were not packaged in most
distros, and not something we would consider packaging in Bigtop, so there's a
fundamental difference there.
> /usr/lib/flume-ng/plugins.d/ needs to be created and owned by flume
> -------------------------------------------------------------------
>
> Key: BIGTOP-1159
> URL: https://issues.apache.org/jira/browse/BIGTOP-1159
> Project: Bigtop
> Issue Type: Bug
> Reporter: Bruno Mahé
> Assignee: Bruno Mahé
> Attachments:
> 0001-BIGTOP-1159.-usr-lib-flume-ng-plugins.d-needs-to-be-.patch
>
>
> Apache Flume expects plugins to be dropped in /usr/lib/flume-ng/plugins.d/.
> But our package do not provide such directory since flume does not ship any
> plugin.
> Apache Flume package should create an empty directory
> /usr/lib/flume-ng/plugins.d/ and owned it.
> So plugins can be dropped automatically as packages into their own
> subdirectories.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
