[hardy] freecol java detection flawed and not enough memory to start
Bug #196264 reported by
Stefan Fleiter
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
freecol (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: freecol
freecol 0.7.2-5 does not start here.
Debugging revealed two problems:
- the java detection can start java with JAVA_HOME not matching java executable
- 128M needs to be increased, I've chosen 192M
I have attached my very first ubuntu patch, so please tell me what to improve next time.
There are still some occurences of telling that 128M are needed in code and doc.
All changes regarding memory should probably be integrated in a dpatch,
I have stopped here to get some feedback first.
Thanks a lot for considering.
To post a comment you must log in.
Thinking a bit more about the problem I come to the conclusion this should be solved
by a generic java wrapper.
It does not make any sense in spite of the fact that many JAVA programms require
the environment variable JAVA_HOME set the java binary is simply managed by the
/etc/alternatives mechanism.
I think there are two possible solutions: alternatives
1. Let a wrapper script set JAVA_HOME matching to the java provider chosen by
/etc/
2. Choose JAVA dynamically by the given JAVA_HOME if set, if not set goto 1. :-)