xine-lib-1.0 wants to pull aalib at any price (it wasn't installed previously). There is a global USE flag aalib which should be used to control the dependency on aalib (like e.g. libsdl is already doing) Reproducible: Always Steps to Reproduce: 1. 2. 3.
Oh, I just saw that the aalib flag was just removed from xine-lib. However, it never should pull in the aalib if it did not exist on the system previously. That si definitly a bug. Using the aalib USE flag is IMHO the right way to go here. (BTW, the same happens with libcaca.) This bug is related to bug 76705. Please mark one of these as dupes if necessary.
Sebastian: If it eases maintenance to remove the option or the option itself causes other problems, it's not necessarily a bug. A quick look at the ChangeLog reveals that it was removed intentionally.
I was the one that asked for it to be put in. I cant find the bug number now, but before, it tried to compile against libcaca and aalib even though they were in use flags. However, another person said he didnt have the same problem, so I tried recompiling without aalib and libcaca, which worked. I dont know why it did that, but you can remove the forced dependancies, since it now obeys the USE flags correctly ( ive just checked, it does compile correctly without libcaca and aalib)
sorry, typo, it tried to compile against libcaca and aalib even though they _weren't_ in use flags
It's Bug 76090.
Chris: Your decision. ;p
seems that this is fixed since the ebuild makes use of the aalib useflag (again)
