On 2020/06/04 18:32, Evan Silberman wrote: > > > On Jun 4, 2020, at 4:13 PM, Alex Free <ale...@mail.com> wrote: > > > > Why are flavors in common libraries a big problem putting aside the > > security issues and quality of code in this case? > > Every flavored library has an exponential impact on the number of > configurations that ports depending on that library must support.
This, plus in some libraries having a new dependency could conceivably change the ABI of the library (e.g. adding struct members) - I think that's unlikely in the case of curl but it's another thing to think about that is avoided by only having one flavour of the library. You also have a problem if some ports start requiring a particular flavour of the library and other ports require some other flavour because you can't have both installed at once.
