i was using ion3, and since ion3-svn contained some fixes for bugs i needed (i.e. a font bug for tabs and a bug which disallowed running opengl apps/games), i wished to switch. i tried using the 20040412 ebuild, but it appeared to not install the various files in the right locations, which made ion3 unable to run as it could not find files it needed. i tried syncing the dirs in system.mk (the file which ion uses to locate the files it needs) with the ones specified in the ebuild, but that did not work either. finally, i edited the ebuild and removed the pathing-bit so that it would use the paths set by the ion devs; this might not be the gentoo way of doing things, but it works, which is a bit more important to me right now. i also made sure the ebuild strips the '-ftracer' flag, which caused compile-errors with ion3 and ion3-svn for me before. in short: this ebuild works and gets the latest version from subversion. Reproducible: Always Steps to Reproduce: 1. ion does not run with the old ebuild. now it does.
Created attachment 30843 [details] ion3-svn-20040506 ebuild
What problems have you been having exactly? It "works for me" as-is. Your version of the ebuild seems to remove everything that renames the ion binary to ion3. The binary should not be named ion because this conflicts with the other ion packages. I'm not going to add the strip-flags -ftracer since if you decide to use strange, aggresive optimisation flags then you should expect problems. This should be fixed by not using strange, aggressive optimisation flags rather than filtering them out in every ebuild :-) There is a bug in the ebuild in that the manual page in ion-man is not renamed to ion3, which I'll fix.
x11-wm/ion3 now also calls its binaries, dirs, etc. ion3. This allows co-existence of ion3, ion2 and ion on the same system. Am closing this bug, but do re-open it if you find other problems. Cheers, Tom
now it works - thanks for updating the ebuild. i think it failed because i was upgrading from ion3 to ion3-svn, and it tried to use an old system.mk for the locations for the files it needed.
