media-gfx/prusaslicer forces the 'adns' use flag for curl. Setting this use flag seems to break other packages on my system. Yet, I've found that removing the adns requirement from the prusaslicer ebuild solves all issues for me (and prusaslicer itself is runnning fine so far). I would therefore suggest to remove this hard requirement and let "the system" decide whether this flag shall be enabled.
What other packages does it break? There's a long history here and prusa does need it.
What function of Prusaslicer depends on the adns flag? (I am asking, because I tried to find something that breaks after removing it, but couldn't.) adns on curl is in conflict with 'threads', which is used by 44 packages on my install. That is the reason I currently always edit the prusaslicer ebuild after every sync. But, of course, it is absolutely possible, that some functionality of PSlicer is broken now without me having noticed.
(In reply to Mr.Chauv from comment #2) > What function of Prusaslicer depends on the adns flag? (I am asking, because > I tried to find something that breaks after removing it, but couldn't.) > > adns on curl is in conflict with 'threads', which is used by 44 packages on > my install. You don't have to globally enable "threads" for all packages. You can enable it just for some. And note that threads is gone from newer versions of curl. Read the bug I linked (bug 853973) and the additional discussion in bug 699632.
(In reply to Sam James from comment #3) > (In reply to Mr.Chauv from comment #2) > > What function of Prusaslicer depends on the adns flag? (I am asking, because > > I tried to find something that breaks after removing it, but couldn't.) > > > > adns on curl is in conflict with 'threads', which is used by 44 packages on > > my install. > > You don't have to globally enable "threads" for all packages. You can enable > it just for some. And note that threads is gone from newer versions of curl. > Also, to be clear, USE=adns on curl was in conflict with USE=threads on curl. In such a case, all you would have to do is 'net-misc/curl -threads' in package.use. > Read the bug I linked (bug 853973) and the additional discussion in bug > 699632. But there's a lot of relevant context in those bugs. Newer curl drops USE=threads entirely, including newly-stable 7.85.0-r2.
Thanks, Sam! Great pointers - learnt something new! Then I guess I'll mask 'threads' for curl until it's phased out.
