Created attachment 325422 [details]
Attached is a new ebuild for Wizorb, "a breakout-style action game with a sprinkle of a Japanese-style RPG." Ebuild is pretty standard fare, except for three things:
1. It's mono-based, and I don't know how to lookup dependencies for something like that. So, the only two dependencies I have listed are the obvious ones: mono and libgdiplus.
2. I got the following QA notice. Hit the suggested link, but I'm not sure how to fix it for a precompiled binary. Figure I could maybe to a QA_PREBUILT= or something, but I'd rather learn the proper fix. Suggestions would be appreciated.
* QA Notice: The following files contain writable and executable sections
* Files with such sections will not work properly (or at all!) on some
* architectures/operating systems. A bug should be filed at
* http://bugs.gentoo.org/ to make sure the issue is fixed.
* For more information, see http://hardened.gentoo.org/gnu-stack.xml
* Please include the following list of files in your report:
* Note: Bugs should be filed for the respective maintainers
* of the package in question and not firstname.lastname@example.org.
* RWX --- --- opt/wizorb/Wizorb
3. Lastly, I'm not really sure how to categorize this. The actual game play (battles and whatnot) is similar to breakout, but in between levels you walk around and talk to people like an RPG. I just used games-arcade for lack of anything more appropriate.
there is a bug in the ebuild. I am on x86 but the ebuild want the amd64 file. you have outcomment the x86? line. but if take the # away than it also fails. but if i delete the amd64? line and change this to the x86? line, than it is working.
And thank you for your ebild! :-)
Yeah, that was kind of by design. You should just comment out amd64? and uncomment x86?.
The reason for this is that, if you have an out-of-tree ebuild, portage must create a digest for all files referenced by the ebuild, which means it must first download (or, in the case of fetch-restricted software, you must manually download) all files and save them in $DISTDIR. Since I don't want to have to needlessly download the 32-bit packages *in addition* to the 64-bit packages of all the games I write ebuilds for, I just comment out the x86? line. That way, portage will only care about creating a digest for the file I actually need.
If this were to ever make it into portage, the digest for both versions will be included in the manifest file, so this issue goes away entirely.