Somewhat ironically, had everyone been less stubborn last year when discussing this topic we could have embedded the EAPI in line X of the ebuild in 2008 and be using it now; instead of still discussing it.
I don't expect new novel ideas out of this thread. I expect the council to defer it again because the arguments are the same as last time and last time they were not convincing enough. I would prefer if the council went one way or the other so that when we are arguing about this in 2010 we can at least say "hey we have support in $PACKAGE_MANAGERs for EAPI on line X since May 2009 so in 3 months we can just switch. We don't have to make the switch; I'm just saying we should add support to hedge our bets. Thoughts? -A
