Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#12637 - limewire-4.18.8-2 hardcodes java path incorrectly
Attached to Project:
Community Packages
Opened by Justin Williamson (epicoxymoron) - Friday, 02 January 2009, 02:59 GMT
Last edited by Roman Kyrylych (Romashka) - Sunday, 11 January 2009, 09:48 GMT
Opened by Justin Williamson (epicoxymoron) - Friday, 02 January 2009, 02:59 GMT
Last edited by Roman Kyrylych (Romashka) - Sunday, 11 January 2009, 09:48 GMT
|
DetailsIn /usr/bin/limewire, the java executable is hardcoded to /usr/bin/java. But Sun's JRE is in /opt/java/bin/java, so that doesn't work.
Sun's JRE creates a shell variable $JAVA_HOME, denoting the location of the java executable. I don't know if the other jre packages also set this variable; if they do, replacing /usr/bin/java with $JAVA_HOME/bin/java would do the trick. If only some JREs set this variable, you could check to see if the variable is set, and use it if it is, falling back on the original hardcoded version. If nothing else, it'd let limewire work with Sun's JRE. if [ "$JAVA_HOME" == "" ]; then jv=/usr/bin/java else jv=$JAVA_HOME fi $jv/bin/java ... |
This task depends upon
Closed by Roman Kyrylych (Romashka)
Sunday, 11 January 2009, 09:48 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#12229
Sunday, 11 January 2009, 09:48 GMT
Reason for closing: Duplicate
Additional comments about closing: