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#7433 - Applications should depend on java-runtime, not jre
Attached to Project:
Arch Linux
Opened by name withheld (Gullible Jones) - Tuesday, 12 June 2007, 15:42 GMT
Last edited by Paul Mattal (paul) - Thursday, 24 January 2008, 03:10 GMT
Opened by name withheld (Gullible Jones) - Tuesday, 12 June 2007, 15:42 GMT
Last edited by Paul Mattal (paul) - Thursday, 24 January 2008, 03:10 GMT
|
DetailsVarious Java applications seem to depend on jre rather than java-runtime, which is provided by both jre and java-gcj-compat. Frostwire, for instance, requires jre, though it should depend on java-runtime, and as a result it can't be used with classpath (unless you feel like installing it without its deps and dealing with the package management nuisances that will follow). To be a bit more friendly to classpath users, these packages really should use java-runtime.
|
This task depends upon
flags tomcat, itext and subversion. I assume jdk can depend on jre...
Naysay within a week, or I will go ahead those. That should then be sufficient to close out this bug.
The depends in kdebase and r are makedepends; it seems to me it's fine to depend on the Sun VM at build-time. Is there an argument about this?