1 |
On Sat, 2005-12-24 at 16:34 +0200, Petteri Räty wrote: |
2 |
> At the moment we have old versions of at least |
3 |
> dev-java/{kaffe,jamvm,sablevm} marked stable. The open source java stack |
4 |
> is starting to be usable but these old versions certainly are not drop |
5 |
> in replacements for the proprietary ones. This in mind I propose that we |
6 |
> move everything to ~arch and re-evaluate them going stable when the time |
7 |
> is right. To give everyone time for objections I plan on moving the |
8 |
> versions to ~arch in January. |
9 |
|
10 |
I think the above statements need some clarification. Are you saying |
11 |
that you want to take the currently-marked-as-stable versions of these |
12 |
packages in Portage and change them to ~arch? If so, that is probably a |
13 |
bad idea for several reasons, chief of which is the many |
14 |
questions/complaints we will all receive when world updates are trying |
15 |
to downgrade packages, or worse, when the new Portage starts complaining |
16 |
about a broken state of the world file due to "No packages being |
17 |
available for [whatever]". |
18 |
|
19 |
Instead I would suggest leaving the existing flags as-is, and bump revs |
20 |
on (new) ebuilds (or newer versions if they exist) and just flag those |
21 |
as appropriate. |
22 |
|
23 |
I think most/all folks using those packages are aware of their limited |
24 |
compatibility with the proprietary VM's. Therefore, the risk of leaving |
25 |
the current versions "stable" is probably minimal. |
26 |
|
27 |
As a worst-case, if you're really concerned about users misconstruing |
28 |
the supposed "stable" status of these packages, you could always add |
29 |
some einfo/ewarn style messages to explain it on those versions. |
30 |
|
31 |
JMHO. |
32 |
|
33 |
Greg |