Hi Simon, > I recalled another concern: libunistring is LGPLv3+, glibc is LGPLv2+. > I don't know how glibc people will think about dynamically loading > LGPLv3+ code
Yes, good point. > A daemon approach with a smaller wrapper library to communicate with it > would avoid this concern too I'm not in favour of implementing bloated or technically bad solutions for the reasons of copyright... > -- would you be willing to relicense libunistring (or parts > of it, given that I'll probably stay at Unicode 5.2 at least until I've > confirmed that it works fine with Unicode 6.0 too) in this case? ... therefore, yes, I'm willing to relicense the parts of libunistring that libidna needs under LGPLv2+. Please come back to me again when you have the complete and minimal list of the modules that you need. Bruno
