From the ebuild: LICENSE="public-domain" I doubt that's correct, and judging by the scary-looking EULA at $HOMEPAGE I wonder if we should ship this package at all.
This package came from Sunrise, where it was labelled with a "Xerox" license: https://gitweb.gentoo.org/proj/sunrise.git/commit/?id=7aa3b8710ece1606e5471494a8b38380c79dd132 No idea why this was lost when the package was moved to the main tree. We definitely need fetch and bindist restrictions here.
Fixed in git. https://gitweb.gentoo.org/repo/gentoo.git/log/?qt=range&q=bc2dd4304cde21bcc5214927e042421480d46dfe...9cf5e51decb366992d1fb56b95ca763390bec80a
Why was a fetch restrict added? Why wouldn't ACCEPT_LICENSE suffice? There is no mirror restriction or anything other than just accepting the license that bars the ebuild from downloading the package.
I digress, it does appear there is a mirror restriction in the license. So why not just restrict it to mirror?
(In reply to Matthew Schultz from comment #3) > Why was a fetch restrict added? If you look at ${HOMEPAGE}, you'll find that the download is behind an "accept license" button. Our standard practice is then to add fetch restriction to the ebuild. We won't bypass upstream's acceptance mechanism by deep-linking to the download page (even if it would be trivial, as in this case).
