* Matt Zimmerman <[EMAIL PROTECTED]> wrote: >> /usr/lib/eclipse and then set symlinks to the 'expected' places in >> /usr/share/eclipse subdirs. > That sounds fine. It would be even better if eclipse would look in FHSish > locations for these things, but symlinks are OK.
Ok, so I will restructure the whole thing... eclipse is very 'single user' minded about everything, no chance yet to get this working FHSish:( >> This will mean, that the 'starter' of eclipse (native, mostly sorts >> out parameter and then passes them on to java) is in >> /usr/lib/eclipse, but would be unusable (IMO), when used from there >> and not via the /usr/share/eclipse symlink. > Does this imply that the wrapper behaves differently depending on the > directory in which it resides? Yuck. I haven't tried, but I think that it won't find the things which will start the rest of eclipse. Anyway, this isn't the problem, which can't be sorted out... Last thing would be to replace the launcher with a simple script. The current wrapper (to make eclipse multi user aware...) anyway implents most options, so doing the rest of them wont be hard. The binary lauchner just does some 'option sorting out' and then starts java with the propper options passed on. The only problem would be error reporting, when java exits with an errorcode. Jan
