Summary: | Provide JavaScript for the dev-java/icedtea6-bin build | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Branko Majic <branko> |
Component: | [OLD] Java | Assignee: | Java team <java> |
Status: | RESOLVED OBSOLETE | ||
Severity: | enhancement | CC: | proxy-maint |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 247140 |
Description
Branko Majic
2011-07-15 21:15:56 UTC
icedtea6-bin is mainly meant for easier bootstrapping of source-based icedtea, so we don't aim to make it feature complete. Is there a reason you can't use the source-based icedtea? The main reason I went for icedtea6-bin in the beginning was due to icedtea package being testing for my arch (and for what matters, for all arches). I've switched to using the icedtea package now, but I still think it would be a nice feature since by emerging the icedtea6-bin you don't have to pull in a lot of other packages required for building the icedtea package. Adding a small elog message to the current icedtea6-bin ebuilds might be useful, though (i.e. let people know that icedtea6-bin is built with a limited set of features and direct them to icedtea for more features). Although this could still potentially be done for icedtea-bin:7, I don't believe it is worth it, especially now that icedtea:8 does not use Rhino for JavaScript. It comes with Nashorn instead. |