The reasons for a unified java launcher would be - java, which most contributors should understand - one ini file for all architectures - one routine to replace them all ;) (set classpath, build cmd line)
sounds worth it to me. ..ede On 01.09.2010 17:34, Larry Becker wrote:
It doesn't seem like the windows launcher would be improved by calling a java launcher. I don't know about other OSs/distros. regards, Larry On Wed, Sep 1, 2010 at 9:31 AM, <edgar.sol...@web.de <mailto:edgar.sol...@web.de>> wrote: On 01.09.2010 15:46, Larry Becker wrote: BTW, I have nothing against retiring the bin directory, but it might break the startup scripts. true, I can check and modify the windows and linux scripts, if we agree on retiring '/bin'. And again I want to lobby for a one for all solution.Let me summarize: - we try to be 'cross-platform' - but can't support different distributions for each operating system - user must be able to change the java runtime parameters (e.g. memory settings) - runtime parameters cannot be changed inside the running environment, but have to be given as parameters Only solution I see is a unified launcher (java) run by native launchers for the different os's. I like the simplicity of startup scripts, but am pretty sure that end users are more confused than supported by them (which should i use, how can i configure ...). regards ede
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
