[
https://issues.apache.org/jira/browse/BIGTOP-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13864665#comment-13864665
]
Peter Linnell commented on BIGTOP-1173:
---------------------------------------
The difference in naming conventions is related to the way Debian insists that
libraries have a numbering system which corresponds to their soname. Suse has
begun to enforce this in openSUSE and SLE 12 will have it throughout. The idea
is to be able to install say libopenssl 0.9x and libopenssl 1.0 in parallel.
For our case, I agree lets be consistent within our own build system.
Hope that helps.
> Inconsistency in libhdfs* packages
> ----------------------------------
>
> Key: BIGTOP-1173
> URL: https://issues.apache.org/jira/browse/BIGTOP-1173
> Project: Bigtop
> Issue Type: Bug
> Reporter: Sean Mackrory
> Assignee: Sean Mackrory
> Attachments: 0001-BIGTOP-1173.-Inconsistency-in-libhdfs-packages.patch
>
>
> There are some inconsistencies regarding our libhdfs packages
> * The versionless symlink is in the -dev deb, but it should be in the other
> * There is no -devel rpm, but there's a comment saying there should be
> * The rpm is "hadoop-libhdfs" as opposed to the "libhdfs0" deb
> The libhdfs deb package appears to be mainly named due to Debian's
> conventions for share library packages, so I don't even know if the third one
> is considered wrong, because the rpm will still be inconsistent with the
> "libhdfs0" deb.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
