Ciaran McCreesh posted <[EMAIL PROTECTED]>, excerpted below, on Fri, 14 Jan 2005 11:23:18 +0000:
> Now, you could argue that x86-sse would be a better name for the flag, > but since we can't really do USE renames it's kinda moot. OK, this looks perfectly obvious to me (on amd64) so I'm obviously missing something since nobody else has proposed it. Doing USE renames or touching all the non-workable ebuilds to change their logic is one thing, but... Why not just create a new amd64-sse USE flag? It'd be local currently, since only two ebuilds could currently use it according to other portions of the thread, but would eventually become a global flag much like the original sse (which should have been x86-sse), as more packages adapted to x86_64/amd64. The other "proper" alternative would be all that work, converting all the current ebuilds to test for both x86 and sse, plus modifying the two that can handle sse on amd64, to test for both of those, and adding similar tests to new ebuilds as the package upstreams adapt them. That prevents USE flag proliferation, but at the expense of rather more work. -- Duncan - List replies preferred. No HTML msgs. "They that can give up essential liberty to obtain a little temporary safety, deserve neither liberty nor safety." -- Benjamin Franklin -- [email protected] mailing list
