This is a new pysol-cardsets. After I wrote it, I found there was a similar bug #46714. Since that bug is more than one year old, I decided to open a new one. This pysol-cardsets-4.40.ebuild is made from scratch (well, the main idea was copied from pydance-songs ebuild), and it is not based on old #46714 bug. Thie ebuild does not overwrite any pysol-4.82-r1 already shipped cardset, so it is very safe to merge and unmerge without problems. Why leave these cardsets as a separate ebuild and not incorporate it into pysol ebuild? Two reasons: 1. these extra cardsets are big (almost 26MB); 2. pysol can run and work perfectly without these extra cardsets (they are only "extra"). Some related pages: http://happypenguin.org/show?PySol-Cardsets http://packages.debian.org/stable/games/pysol-cardsets If someone questions why we should include pysol-cardsets into portage if they are not available anymore on official, I tell you: Debian guys can have it, why us, Gentoo users, could not?
Created attachment 75938 [details] pysol-cardsets-4.40.ebuild
huh, just a note: I marked all three arches (amd64 ppc x86) as stable in ebuild. Ok, this is wrong, but since this ebuild does not compile anything, just places some files in a directory, I can't see why it would not be "stable".
i just installed this ebuild and can confirm that it's working nicely on x86... i'd very much like to see this in portage, so, just a here-here
ebuild is now in portage. Thanks
I know this took one year to be included, and is now marked as fixed... But right now I thought if it would be better to include pysol-cardsets as an useflag inside main pysol ebuild...
