Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
List Archive: gentoo-java
On Sat, 2005-12-24 at 16:34 +0200, Petteri Räty wrote:
> At the moment we have old versions of at least
> dev-java/{kaffe,jamvm,sablevm} marked stable. The open source java stack
> is starting to be usable but these old versions certainly are not drop
> in replacements for the proprietary ones. This in mind I propose that we
> move everything to ~arch and re-evaluate them going stable when the time
> is right. To give everyone time for objections I plan on moving the
> versions to ~arch in January.
I think the above statements need some clarification. Are you saying
that you want to take the currently-marked-as-stable versions of these
packages in Portage and change them to ~arch? If so, that is probably a
bad idea for several reasons, chief of which is the many
questions/complaints we will all receive when world updates are trying
to downgrade packages, or worse, when the new Portage starts complaining
about a broken state of the world file due to "No packages being
available for [whatever]".
Instead I would suggest leaving the existing flags as-is, and bump revs
on (new) ebuilds (or newer versions if they exist) and just flag those
as appropriate.
I think most/all folks using those packages are aware of their limited
compatibility with the proprietary VM's. Therefore, the risk of leaving
the current versions "stable" is probably minimal.
As a worst-case, if you're really concerned about users misconstruing
the supposed "stable" status of these packages, you could always add
some einfo/ewarn style messages to explain it on those versions.
JMHO.
Greg
|
| Attachment: |
|
signature.asc (This is a digitally signed message part)
|
|