wine-1.6.1 is ancient. Even stable is 1.6.2. Have you run emerge --sync recently ?

In my experience, the problems of the sort you report are frequently dealt-with by emerge -quDN @world and if there are still conflicts, USE=-someflags emerge -q1 blockingpackage until emerge -quDN @world works._________________Michael Mounteney

wine-1.6.1 is ancient. Even stable is 1.6.2. Have you run emerge --sync recently ?

In my experience, the problems of the sort you report are frequently dealt-with by emerge -quDN @world and if there are still conflicts, USE=-someflags emerge -q1 blockingpackage until emerge -quDN @world works.

This is only appropriate if the OP wants to run unstable Wine. In the context of package.accept_keywords, which is also handled under the older name package.keywords, atoms without a keyword list are implied to mean ~arch for the current architecture, so it would be sufficient and more portable to echo the atom without an architecture.

Wine is unstable but it's really stretching the interpretation of stable/unstable when 'stable' means an old version of a package in heavy development. 'Stable' is supposed to mean well-tested and with no or few bugs outstanding, but any non-current version of wine has the implicit 'bug' that it lacks full implementation of certain Windows features. So I say: go with latest for wine. Other points conceded._________________Michael Mounteney