<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Hi,<br>
      <br>
      On 17/07/2013 14:04, Ondřej Surý wrote:<br>
    </div>
    <blockquote
cite="mid:CALjhHG-V_WCAvoZEKMjqyb2Ch01cSc3+aROd50BUU93EK_+v+A@mail.gmail.com"
      type="cite">
      <div dir="ltr">On Wed, Jul 17, 2013 at 1:02 PM, Alexey Melnikov <span
          dir="ltr">&lt;<a moz-do-not-send="true"
            href="mailto:alexey.melnikov@isode.com" target="_blank">alexey.melnikov@isode.com</a>&gt;</span>
        wrote:<br>
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">On
              16/07/2013 14:23, Ondřej Surý wrote:<br>
              <blockquote class="gmail_quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex">
                Hi,<br>
              </blockquote>
              Hi Ondřej,
              <div class="im"><br>
                <blockquote class="gmail_quote" style="margin:0 0 0
                  .8ex;border-left:1px #ccc solid;padding-left:1ex">
                  I have realized one quite serious problem in plugin
                  loading with recent SONAME bump.<br>
                  <br>
                  The plugins are versioned, but the library ignores
                  that and looks for .so files in the plugins directory.<br>
                  <br>
                  This basically prevents the gradual transitioning from
                  one SONAME to another, since at one point in time you
                  have to replace the plugins with one version or
                  another.<br>
                  <br>
                  I would propose to change the mechanism to look for:<br>
                  <br>
                  .so.&lt;SONAME&gt;<br>
                </blockquote>
              </div>
              How can libsasl library know expected &lt;SONAME&gt;
              information?</blockquote>
            <div><br>
            </div>
            <div>I expect that one should be able to compute it at
              compile time from the info passed to libtool.</div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    So you are suggesting that this information is hardcoded into
    libsasl during build time?<br>
    <br>
    How would this work with third party plugins (which don't have to
    use the same &lt;SONAME&gt;)?<br>
    <br>
    There are also some platforms which might not be generating
    .&lt;SONAME&gt; at all. The code needs to be generic to handle these
    as well.<br>
    <br>
  </body>
</html>