There is no reason for the wine ebuilds to depend on the yacc package, for the reasons provided: - bison provides identical parser generator functionalities. From the bison(1) man page: "Bison is a parser generator in the style of yacc(1). It should be upwardly compatible with input files designed for yacc." It also follows that bison imitates output file naming by specifying the -y flag. - The configure script provided with the wine source checks for the existence of both yacc and "bison -y". - bison is required as a core Portage package (since it is listed in sys-devel); thus installing yacc would be rather redundant. (We could also make a claim that there is never an instance in which yacc will be required, since it is superceded by bison. Perhaps defining the two to provide a virtual package would be a better compromise?) My only verification of this is modification of wine-20031118-r1.ebuild by removing the line reading "dev-lang/yacc" in the DEPENDS variable. Wine then successfully compiles and merges, without ever installing yacc. Reproducible: Always Steps to Reproduce:
apologies for not line-wrapping the description. any way to fix retroactively?
wrapping has been fixed. And, I'm not sure about wine (you're prolly right) but in some cases the bison -y yacc pretence isn't enough, as it doesn't handle the obscurities of yacc. (Google around for it and you'll see some examples)
yacc dep removed from wine-20031212
