v86d can use two backends for executing x86 code: lrmi (available on x86 only) and x86emu (works on both x86 and amd64). sys-apps/v86d has a local USE flag called 'x86emu' which makes it possible for x86 users to use x86emu instead of lrmi. This flag is ineffective on amd64, where the x86emu backend is always used, regardless of the state of the USE flag. Making 'x86emu' for sys-apps/v86d forcibly enabled on amd64 would make it less confusing for the users, who can wonder whether they should enable it or not on amd64.
Should be rather masked than forced.
Well, I don't really agree with that. The flag enables some functionality, which is always enabled on amd64. If it is added to package.use.mask, then the users will see: [ebuild R ] sys-apps/v86d-0.1.6 USE="-debug (-x86emu)" 0 kB which suggests that they can't use x86emu and are therefore using lrmi (the default backend), whereas: [ebuild R ] sys-apps/v86d-0.1.6 USE="-debug (x86emu)" 0 kB which the users would see if the flag was forcibly enabled, would suggest that the x86emu backend is always enabled (which is in fact the case). If you think the above reasoning is incorrect, could you please elaborate as to why that is?
Done. It's now forced on all non-deprecated amd64 profiles.
