[
https://issues.apache.org/jira/browse/DISPATCH-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17345042#comment-17345042
]
Jiri Daněk commented on DISPATCH-1332:
--------------------------------------
bq. The current arrangement is confusing and makes it unnecessarily difficult
to use them both.
libqpid-dispatch.so is a private library that is intended to be used only by
dispatch, it should not be available for linking systemwide. The same is
probably true about the dispatch python modules. So I feel that putting them
into a nonstandard directory is perfectly fine and desirable. In contrast to
Proton, which is intended for public consumption, so that installs itself to be
easily accessible.
I am not saying that everything is as it should be with Dispatch. Using {{lib}}
instead of {{lib64}} looks like a bug... But the private C and Python libraries
have to be tucked to the side, out of the normal import paths, so that users
can't just start using them as if those were public APIs. The packaging guides
for Debian and Fedora should have hints what are appropriate locations.
> Reconcile install directories and content
> -----------------------------------------
>
> Key: DISPATCH-1332
> URL: https://issues.apache.org/jira/browse/DISPATCH-1332
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Tools
> Affects Versions: 1.6.0
> Reporter: Charles E. Rolke
> Priority: Major
> Attachments: opt-local-tree-full.txt
>
>
> An installation of qpid-proton and qpid-dispatch is created with a cmake
> install where both projects use:
> {{cmake -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=/opt/local}}
> qpid-dispatch places a 64-bit .so file in /opt/local/lib when it rightfully
> belongs in /opt/local/lib64.
> Further investigation of the install directories reveals some discrepancies
> between qpid-proton and qpid-dispatch installation hierarchies. Please see
> attached _tree_ listing. One might expect them to be symmetric where
> possible. The current arrangement is confusing and makes it unnecessarily
> difficult to use them both. Note that self tests force PATH and PYTHONPATH to
> reflect the discovered locations but the values they use are not always
> practical for simple stand-alone product usage. Using the /opt/local install
> prefix then requires a PYTHONPATH like this;
> {{/opt/local/lib/python3.7/site-packages}}
> {{/opt/local/lib64/proton/bindings/python}}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
