[
https://issues.apache.org/jira/browse/BIGTOP-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13577601#comment-13577601
]
Sean Mackrory commented on BIGTOP-463:
--------------------------------------
The only problem I've run into is that invoking bigtop-detect-javahome takes 5
lines instead of 1 - any time you reference it you have to add logic for both
locations. As I've seen while adding a bigtop-detect-javalibs scripts for
BIGTOP-504, this will just get worse as more functionality is added to
bigtop-utils. I don't know if others have run into any problems of a more
technical nature - but I just think it will make the wrapper scripts a lot
cleaner and quite possibly prevent mistakes in the future.
The downside to doing this is that packages that depend on bigtop-utils will
now need to specify that they need a least bigtop-utils 0.6.
> should we reconsider /usr/lib vs. /usr/libexec decision?
> --------------------------------------------------------
>
> Key: BIGTOP-463
> URL: https://issues.apache.org/jira/browse/BIGTOP-463
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Sean Mackrory
> Fix For: 0.6.0
>
>
> I keep running into issue where /usr/lib vs. /usr/libexec becomes a pain. In
> theory it is doing the right thing, but in practice it complicates
> maintenance and doesn't seem to give us any major benefits. Given that the
> only 2 packages that use /usr/lib vs. /usr/libexec are bigtop-utils and
> bigtop-jsvc, perhaps its not too late to reconsider and keep their content
> under /usr/lib/bigtop-utils ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
