On Sat, Jun 30, 2012 at 12:25 AM, Yang Tse <yangsita_at_gmail.com> wrote:
> In my previous message, I wrote...
>
>> test2017 to test2022 disabled for now, until build systems are capable
>> of detecting libmetalink version being used at run-time or at least at
>> build time. Given the broad variety of build systems and platforms
>> curl supports, version provided by libmetalink.pc is not enough to
>> achieve this requirement.
>
> I'll try to be more precise...
>
> Well, libmetalink.pc might be enough for configure to detect
> libmetalink version. But if configure doesn't locate libmetalink.pc
> then libmetalink should not be used in that build.
>
> For other build systems libmetalink.pc certainly isn't enough. For
> reasons you perfectly understand libmetalink should not be used in
> curl without checking its version. Preferably at run-time given that
> it might be used as a shared library.
>

My understanding is that we need version check API, say,
metalink_check_version in libmetalink and do runtime version check
from curl code invoking the new API. Is it correct?

Best regards,

Tatsuhiro Tsujikawa

> HTH
> --
> -=[Yang]=-
> -------------------------------------------------------------------
> List admin: http://cool.haxx.se/list/listinfo/curl-users
> FAQ:        http://curl.haxx.se/docs/faq.html
> Etiquette:  http://curl.haxx.se/mail/etiquette.html

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-users
FAQ: http://curl.haxx.se/docs/faq.html
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2012-06-29