| 1 | | Also, many packages that you compile yourself, don't care which of the two libiconv is the default,as long as you stick with it. Only pre-compiled packages (again, like Haskell) may be unhappy with the default, and require special treatment. |
| | 1 | Also, many packages that you compile yourself, don't care which of the two libiconv is the default,as long as you stick with it. They'll just compile against the correct .h files that map the correct function names, and link against the available library. No-brainer. |
| | 2 | |
| | 3 | Only pre-compiled packages (again, like Haskell) may be unhappy with the default, and require special treatment. And again, those packages that include ''shared'' libraries dependent on {{{libiconv}}} are simple (if tedious) to remedy. |
