OpenSong, an opensource presentation package geared towards churches and presentation of worship music http://sourceforge.net/project/showfiles.php?group_id=108754&package_id=117409 the tar.gz is a binary that works on linux. I haven't tried compiling myself yet, but plan to soon if I can get instructions. Otherwise, I may just create a sample ebuild using the binary distribution.
http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=1 http://devmanual.gentoo.org/
The compile-time and run-time requirements for REALbasic-based applications can be found here: http://www.realsoftware.com/products/realbasic/requirements/ REALbasic 2007r2 Standard was used for compiling the posted version. 2007r3 is available but has a known memory leak in XmlDocument.ToString, which is used rather heavily in OpenSong. There was some tweaking done on the window layouts to correct a visual issue with drop-down combo and list boxes. The height for each of these was changed from 20 to 30 and the controls below these were moved and sized to accommodate the change. These changes were not checked into the SourceForge subversion repository. For compilation, the JPG files in OpenSong Images must be available to the compiler. At runtime, OpenSong looks for four folders in the same directory as the executable: OpenSong Defaults, OpenSong Languages, OpenSong Scripture and OpenSong Settings. Those and the opensong executable are the only items that need to be installed on a target system. If you "svn checkout" or "svn export" the source tree you will get all of these folders. The V1.1 code is at https://opensong.svn.sourceforge.net/svnroot/opensong/source/tags/V1.1 and the latest snapshot lives at https://opensong.svn.sourceforge.net/svnroot/opensong/source/trunk. At the moment (revision 253) these are the same.
Upstream of this project is ACTIVE (which is a nice change comparing to all those zombies I've had to look at lately), unfortunately it still depends on RealBasic to compile so making a proper ebuild would be problematic due to the lack of a FOSS compiler. Still, if there is user interest it shouldn't be too difficult to create a bindist-based package... *Is there* still any interest in having this included in Portage?
I haven't used this for years now, so sadly no.
Okay then, closing the bug.