I've checked it several times, and not found aisleriot in the gnome-games package. The doc and icons are there, but not the binaries. I also try to find an explanation, but don't. So, why is aisleriot absent from the package ? Reproducible: Always
You didn't provide your emerge --info nor emerge -pv gnome-games so I'm just assuming you don't have guile use flag enabled. This use flag is needed for some games and notably card games.
I think there is something to improve here, as USE=guile doesn't describe aisleriot in any way. Also the doc and icons getting installed without it sounds like a bug we could try fixing. I suggest an einfo with USE=-guile saying that aisleriot will not get installed due to the lack of that USE flag
additionally I've had the idea of splitting up gnome-games after gnome-python-* int he same manner, but that's a blue sky idea... If that were to happen, then it would be more obvious, as you'd have a aisleriot ebuild as well, that hard depends on guile, with gnome-games being a meta with guile USE flag
The whole confusion stems from the fact that the flag is misnamed. $ euse -i guile [- ] guile - Adds support for the guile Scheme interpreter Please stop naming use flags after which dependency they pull in and start naming them after what they really do in the gnome ebuilds.
That's how everyone does it. Unfortunately. Just going and adding tons of local USE flags doesn't help all that much either. Comes back to the metadata.xml USE flag describing for a particular packages case, I'd say.
(In reply to comment #5) Unless someone fixes current tools (such as euse) to display that info, these descriptions are just burried there without anyone knowing.
So therefore until such time, that the tools are improved, this will stay only visible as an einfo after the installation...
Why not use EAPI=1 for being able to use USE +guile ? This way most users would get aisleriot installed and, if they would know why guile USE flag is needed, maybe a comment could be added to ebuild
gnome-games 2.22 now has an explicit message about this.
closing, 2.22 is on its way to stable.