Hideki Yamane wrote: > Hi list, > > I made a package that uses ~/.eclipse/eclipserc file for users' configuration. > But as the comment in Bug#402077(*), it seems not to be recommended. > It works with eclipse3.4 in Debian but not with 3.5 in Ubuntu 9.10. > > So, what should I use for unless eclipserc? Could someone tell me, please? > > > *) http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=402077 > Hi The reason why #402077 is tagged "wontfix" is that we intended not to use eclipserc anymore. The two primary reasons for having it have been solved: We no longer have to search for JVMs on start up and the "Check for internal browser" warnings have caused nothing short of 4 bug reports, which displays its inability to properly detect browser support on a Lenny or Squeeze. It never occurred to me that other packages actually used this file; so I presumed we could just remove it. So... What kind of configuration do you need and how should it be handled? If it is just environment variables, then we can probably just keep sourcing it (or another file to avoid problems with old user configurations). If you want to pass specific options to either eclipse or the jvm, then I would prefer that happened via eclipse.ini. The problem is that if eclipse is started with command line arguments it ignores eclipse.ini and users expect eclipse.ini to be parsed (because upstream's documentation explains how everything is done via that file). I admit it would better if we could get a "per user" eclipse.ini; sadly I have not had time to research if this is possible. ~Niels PS: I CC'ed you because I was unsure if you were subscribed to this list.
Attachment:
signature.asc
Description: OpenPGP digital signature