[
https://issues.apache.org/jira/browse/BIGTOP-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14081342#comment-14081342
]
Sean Mackrory commented on BIGTOP-1159:
---------------------------------------
{quote}Oozie is a bad example as it does crazy things anyway.{quote}
Won't argue with that! Won't argue with LSB / FHS either, but I consider
user-provided plugins to be much more "variable" (in their presence - even
though the files themselves should be treated as read-only) than files in /usr
that are managed by packages. Just in terms of their behavior, I would expect
removing a package to remove everything from /usr/lib, but I'd expect stuff to
get left behind in /var/lib, so it feels like the right place for plugins to be
to me.
Nevertheless, it was just a suggestion, so if you still disagree you have a +1
to commit from me.
> /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)
