it seems that since we've added gcc-4 ebuilds to portage, people think we're supporting it ... we do and we dont ...
if you want something fixed for gcc-4, then create a good patch yourself, file a bug, and include the patch ... if the patch doesnt suck, we'll probably add it to portage ... if it does suck, we'll be inclined to inform you of such suckage and ask for a patch that doesnt suck quite as much (preferably a lot less)
we're not about to start trying to reproduce the failure and tracking it down ourselves ... that step of support wont happen until gcc-4 is actually released
so to recap:
if you're a big enough boy to try to use gcc-4, you're a big enough boy to fix bugs yourself
-mike
-- [email protected] mailing list
that's how it was with gcc-3.4 already and will go just as smooth with profile masks once there is a actual first release
we will as usual welcome user contributions and look forward to what the big enough boys will hand in for us devs to swiftly apply/test/commit
good times
Daniel
P.S. i know there is no signature right now, ill be working on this
-- [email protected] mailing list
