On 09/16/2011 04:37 AM, Oliver Burger wrote:
2011/9/10 Vinet Raphaël<[email protected]>:
Hi,
Not a problem for me but that it is something a little bit illogical (for me)
with chromium packages in core (+ updates) repository for mageia 1.
Till yesterday (see bug https://bugs.mageia.org/show_bug.cgi?id=2589) it was
logical: we had a stable version in 11, a beta version in 12 and unstable
version with 13.
Now we have :
- stable - 11.0.696.68-1.mga1 in core release
- stable - 13.0.782.220-1.1.mga1 in core updates (bug 2589)
- beta - 12.0.742.53-1.mga1 in core release
- unstable - 13.0.761.0-1.mga1 in core release
==>
1. For me (just an opinion 'cause i only use stable versions) in core
release/core release updates we must not have beta or unstable versions.
Never, core release / core updates are only for stable rpm's in all cases.
2. If beta and unstable have their places un core (updates) repositories, is
it normal that we don't have beta and unstable versions> last stable version
?
What do you think ?
Where else to put them but in core? They are clearly not tainted or
nonfree. And Chromium beta and unstable versions aren't all that
unstable usually and if you are doing web-development it can be quite
useful to have theese newer versions available.
So the only issue left is chromium-stable being newer tthen
chromium-beta or -unstable, which doesn't harm anyone I think.
It's just that nobody pushed the updates of the other two...
Oliver
Well, except that as a chromium-beta user, not only did I miss out on an
update to the latest version and whatever features it might have, I was
never informed that it had been added to the repositories at all. I only
found out when I read it here.
When I installed Mageia, I carried over my chromium configuration from
Mandriva. But Mageia's chromium-stable didn't like that because Mandriva
was at version 12 and Mageia was version 11. So I installed the beta
version, because it would work and seemed a good compromise between the
stable and unstable versions. But I expected a progression, with the
latest version moving through unstable to beta and then to stable, not
leaping over both.
If that's the way it's going to be maintained, it appears that if I want
to get the latest security fixes and features, I'd better stick to the
stable version myself.
TJ
