Following the updated advance MAME and MENU ebuilds, here it is the Raine ebuild. This is an even nicer arcade roms emulator, which although targets a smaller set of games, those emulated bring faster emulation and/or other extras compared to MAME. Together with it, I'll just post an updated allegro ebuild, version 4.1.5, which supposedly is a development version. Yet, as explained on allegro's home page, it doesn't mean it is not stable. This ebuild (raine's) includes a couple patches to allow compilation with this newer allegro. You might think why the development allegro if it is not a requirement for Raine. The answer is that ALSA support in allegro is for 0.5 versions, which are way outdated in our Gentoo systems, and 4.1.x include arts support, which for those using KDE is a more than decent substitute for ALSA. Try it both in console and X. For some modes (the faster ones) root privileges are needed, read the doc for more info. I've some problems with full screen modes and with sound which I haven't solved yet. They belong to Raine and bugs/fixes should be probably sent to Raine's author.
Created attachment 5905 [details] raine-0.36.2.ebuild To go under app-emulation
you forgot to include the patches
Created attachment 5916 [details] raine-allegro_4.1.5_fix.patch You're right, here you have it. Place in $FILESDIR/
Created attachment 5917 [details] Raine.desktop Put this on $FILESDIR/ too, it is a menu entry for KDE. If anyone can provide one for Gnome, it would fit well.
By the way, if you look closely at the ebuild you'll see a line which says: RESTRICT=nostrip I added that to avoid the stripping of 'raine' which emerge does automatically. I didn't see that documented anywhere, but found it in ebuild.py Is there any other way to do it? Oh, the reason to do that is that after installing I add 'raine.dat' to 'raine', with 'exedat' from allegro, as explained in some installation tips on the web - they were for DOS, but apply here as well-. The install, by default, puts raine in /usr/bin and raine.dat in /usr/share/raine - actually, those are the places I put in the makefile. The problem is that to make raine work you have to be in /usr/share/raine, or it will claim it can't find raine.dat Thus merging both is a cleaner solution. When emerge strips the binary, it breaks this merge.
actually if you look in the man page for ebuild (section 5), all the options for the RESTRICT variable are explained
Yes, you are right. I had only read man(1) and the html guides which AFAIR - I could be wronng again, of course - don't mention it. Interesting the fetch and nomirror options too. It seems not everybody is aware of those features or I bet there would be more ebuilds with RESTRICT used. I just 'grepped' the entire portage tree and did not find a single RESTRICT reference.
root@vapier root # grep RESTRICT /usr/portage/*-* -R | wc -l 80
There are days one should be stay in bed... I'm ashamed. I just realized what my problem was, I omitted an 'xargs' root# find /portage/ -name '*.ebuild' | grep -n 'RESTRICT' when I should have put: root# find /portage/ -name '*.ebuild' | xargs grep -n 'RESTRICT' If I don't use find, grep goes through all my built packages on. I'll probably move /portage/packages somewhere else... So SpanKY, is Raine working for you? I don't know if I should write to the author about the problems I have. I'd like to hear other people's sucess/failure before doing so.
its all set now ... http://cvs.gentoo.org/cgi-bin/viewcvs.cgi/gentoo-x86/app-emulation/raine/raine-0.36.2.ebuild?rev=1.1&content-type=text/vnd.viewcvs-markup
