esound-0.2.38-r1.ebuild contains a conditional to apply an interix patch. The conditional is interix3. The patch adds guards for interix, hence I assume it is conditional for interix != 3.5, because other interix versions do work or something. This style of patching reminds me pretty much of the notorious Gentoo for Mac OS X age, and I have several (including personal) reasons to dislike this modus operandi. Can't you do something like #if __INTERIX > 3 or write a configure check to set a proper guard? Upstream can't ever accept this patch, and we want to get rid of patches in Gentoo, and send them upstream instead, which means a conflict. Please discuss. This kind of patching also brings us a step further away of main tree integration, as it is in general not just my disagreement with this kind of patching, but that of the entire dev community.
the only option there would be writing a configure check. __INTERIX is a value-less define, and there is no other one describing the host system (correctly). You're probably right, that the patch isn't that good. I first ported esound to interix 5.2 and 6.0 so 3.5 was somehow like a stepchild :) it was just hacked in there afterwards.
this probably won't ever get fixed.
