Changes between Version 1 and Version 2 of Ticket #57821, comment 3
- Timestamp:
- Dec 28, 2018, 3:08:44 AM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #57821, comment 3
v1 v2 3 3 But this is a **Macports** version of {{{libiconv}}} - therefore the only OS it should target (e.g., via Macports patches) should be MacOS, right? 4 4 5 Also, the **name of the library** does collide - which makes it impossible to use packages that require, e.g., a modern (Macports-installed) OpenSSL that resides in {{{/opt/local/lib}}} and OS-provided libiconv that resides in {{{/usr/lib}}}. If I don't add {{{/opt/local/lib}}} - then **all** the older OS-provided libraries would be used, in which case what's the point of using Macports? And if I add {{{/opt/local/lib}}} before the default {{{/usr/lib}}} - then {{{/opt/local/lib/libiconv.dylib}}} gets used because it carries the same name as {{{/usr/lib/libiconv.dylib}}}. 6 7 If the developers were concerned about the conflict with an OS-provided iconv library - why on earth did they keep **exactly** the same name? To ensure the conflict would occur? Comrade Stalin used to say about such cases "Ни Богу свечка, ни чёрту кочерга". 5 8 6 9 7 > If you need help resolving it, you could ask on the MacPorts mailing lists 10 > 11 > If you need help resolving it, you could ask on the MacPorts mailing lists 8 12 9 13 Could you please point me at the appropriate mailing list? Thanks!