>>> Another option is to use the start script supplied in the bug: >>> >>> http://bugs.gentoo.org/show_bug.cgi?id=128356 >>> http://bugs.gentoo.org/attachment.cgi?id=97807 >>> >>> but I'm not sure how to get it to install somewhere useful. Just >>> putting it in the files dir, I don't think anything happens with it. >>> Any pointers on that? >> >> I added an alternate ebuild to the bug. It doesn't need external >> runner scripts. With it JAlbum-.8.5.1 seems to start-up nicely even on >> amd64, asks for some kind of login (I canceled out from that screen), >> and then allows one to ... well, design album covers, I guess. :) >> >> That's how far I tried it. Now it starts up, but I still don't know if >> all the dependencies got properly laid out. And reading into the >> ebuild should reveal many pieces still needing work. >> >> -- >> Arttu V. > > Thank you very much Arttu. It works great! JAlbum is a photo > management app BTW. It's really slick. > > So all the new dependencies were required to create /usr/bin/jalbum? > > - Grant
I'm sorry Arttu, I spoke too soon. I only did a cursory check before. The program doesn't seem to work at all when installed via the new ebuild. The only way I can get the program to run properly is to install via the old ebuild, 'chmod 755 /usr/lib/JAlbum/startjalbum.sh', 'cd /usr/lib/JAlbum', and './startjalbum.sh'. I'd like the ebuild to leave the user with a command that can be put into a simple launcher though. Should I have the ebuild chmod, cp, and alter the contents of the .sh script to provide the full path of JAlbum.jar so cd isn't necessary? - Grant
