Latest version marked ~mips is 0.99.3, that is the "old school" ebuild (I took it over from -r1, with cleanups and fixes). Can newer version be tested and marked ~mips? Thanks, Diego
*** Bug 88726 has been marked as a duplicate of this bug. ***
I think this is going to be a big problem at this point. Seems to me like mips team can't really continue handling xine-lib and related packages, as they can't test them, the current version of xine-lib are vulnerable to multiple security issues for starting. I think that the issue can be solved by use.masking "xine" useflag in mips profiles and then removing mips keywords from xine-lib, xine-ui and the rest of frontends that are currently marked (~)mips. Please respond on this call.
Mike, media-libs/emotion has an hard depend on xine; can you drop that and put it under xine useflag, or drop mips keywording?
xine is already optional in the cvs version of emotion as for the snapshots, those require xine ... i didnt make xine optional in e17 cvs until after those snapshots were made
Well can you do something for that then? Currently it would require the entire e17 to be removed from ~mips to remove xine-lib.
Okay I'm committing media-video/elation and media-libs/emotion with KEYWORDS overwrote in ebuild, and no more ~mips keyword. Then I'll commit xine-lib.
media-libs/xine-lib committed, ~mips keyword dropped, thank you for bearing with this :P When there'll be someone who can maintain the ~mips/mips keywording for xine, I'll be looking forward to see it again :)
