Uploaded image for project: 'AMQ Clients'
  1. AMQ Clients
  2. ENTMQCL-467

[legacy-cpp] Move "internal" shared libraries out of /usr/lib64

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Won't Do
    • Icon: Minor Minor
    • None
    • None
    • legacy-amqp-cpp-client
    • None
    • Hide
      [Note from Justin on how this information has to be documented in the release notes: I don't think we'll ever address ENTMQCL-467. If we describe it as a known issue, that might be misleading, because we have no plan to change it at ths point. I think I'd put it in the "important notes" section of the RNs.
      And finally, libqpid-proton.so will definitely not be hidden away. It's not supported API in product at this point, but it is public API upstream, so it has to stay where it is.]
      Show
      [Note from Justin on how this information has to be documented in the release notes: I don't think we'll ever address ENTMQCL-467 . If we describe it as a known issue, that might be misleading, because we have no plan to change it at ths point. I think I'd put it in the "important notes" section of the RNs. And finally, libqpid-proton.so will definitely not be hidden away. It's not supported API in product at this point, but it is public API upstream, so it has to stay where it is.]
    • Not Yet Documented

      Having "internal" libraries in this standard directory is messy, both for customers ("Can I link with this or not?") and QE ("Does ABI check failure between updated libraries matter here?").

      It would be nicely resolved if internal libraries were moved elsewhere, the way it was done with qpid-dispatch router.

            jross@redhat.com Justin Ross
            jdanek@redhat.com Jiri Daněk
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: