| 1 |
On Wednesday 28 July 2004 1:55 pm, Phil Richards wrote: |
| 2 |
> Isn't that what using ~x86 you might expect? If there is |
| 3 |
> a view that the beta is generally ok (and it clearly doesn't |
| 4 |
> cause problems for everybody) then ~x86 seems reasonable to get |
| 5 |
> the ebuilds sorted out ready for "full" release of 3.3. |
| 6 |
|
| 7 |
Getting everyone to agree on what ~ means has not been done yet. |
| 8 |
|
| 9 |
However, the handbook sez: |
| 10 |
|
| 11 |
"The ~ARCH stadium means that the package works for the developer in charge |
| 12 |
of the package, but that the package hasn't been tested thoroughly enough |
| 13 |
by the community to be placed in ARCH. ~ARCH packages usually go to ARCH |
| 14 |
after being bugfree for a sufficient amount of time. " |
| 15 |
|
| 16 |
In this case Caleb followed policy. He's doing the right thing. |
| 17 |
package.mask is for things that we know (before or after the fact) cause |
| 18 |
significant breakage. That's not the case with KDE 3.3 beta 2. |
| 19 |
|
| 20 |
I will agree that there are some points of confusion with it, such as: |
| 21 |
|
| 22 |
- After installing 3.3 beta 2, new KDE-dependent applications will compile |
| 23 |
against 3.3 libs even though you may still be using 3.2. |
| 24 |
- kdegraphics was not available at the same time as the other packages, for |
| 25 |
whatever reason. |
| 26 |
|
| 27 |
In any case, ~ is bleeding edge and users have to understand that bugs are |
| 28 |
expected... that's the whole point. To find the bugs and make it stable. |
| 29 |
|
| 30 |
Cheers, |
| 31 |
Dylan Carlson [absinthe@g.o] |
| 32 |
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x708E165F |
| 33 |
|
| 34 |
-- |
| 35 |
gentoo-dev@g.o mailing list |
Archives