galeon-1.3 is still masked, with the comment # <liquidx@gentoo.org> (09 Mar 2003) # depends on moz gtk2 which isn't well tested yet >=net-www/galeon-1.3.2 but I think this is somewhat outdated? mozilla gtk2-port is prretty ok by now, the stable ebuild doesn't require WANT_GTK2 anymore, and epiphany is using it as well and is not masked. I think the current galeon-1.3 has deserved to enter into the full testing-distribution. :)
Same goes for Mozilla - this is also masked in packages.mask - maybe it's time to move it to ~arch since every product out there like fx. epiphany and evolution relies on Mozilla 1.3+ for optimal usage. There's is also no good reason given in packages.mask to the mozilla mask, so could one at least be made - I know it's suppose to be unstable but isn't that what we have ~arch for, it seems a bit extreme to block it completely.
~arch is not for unstable stuff, but for testing, what means suspected as stable. But notice that only mozilla-1.3a is masked, and no other versions. It's a little bit silly by now, as version 1.3-r2 is already stable. looks like someone should clean up the mask-file a little. ;)
darko, you have a point there with galeon-1.3 and epiphany. except for the fact that this would force people who are using galeon-1.2 with gtk1 mozilla to recompile mozilla with gtk2. we'll think about how to make that upgrade as smooth as possible. about the mozilla's mask in p.mask, 1.3a is actually not the same as 1.3_alpha (see the developer policy/ebuild howto on versioning). it was a cover for a mistake when a dev accidentally named 1.3_alpha 1.3a, and hence, portage thought 1.3 final was older than 1.3a. in this case, the a does not stand for alpha, but a code revision, see openssh and galeon for example. actually, i fixed the 1.3a p/mask just last night before you mentioned it, but at least some of us are attentive :)
Ok, now I understand the versioning problem of mozilla. And it's obviuos one wouldn't want to promote misnamed 1.3a over the later 1.3. But does this really have an effect, since the old 1.3a ebuild vanished by now? As for galeon 1.2 vs 1.3: having only 1.2-versions in stable and 1.3 in testing should do the trick, no? If you start caring to make the testing-releases failsafe for the average user, this heads into a wrong direction imho, as someone using ~arch should know exactly what he's doing and how to handle an upgrade there.
and no commenter #2, ~arch isn't for unstable stuff, it's for testing ebuilds mainly.
well, the 1.3 series is development stuff. When it hits 1.4 (or 2.0?) it should be unmasked. This is really not related to the whole gtk2 issue (altough thats also a concern). On the other hand the galeon guys seem to think its pretty stable, so with moz 1.4 going stable we might reconsider that and take it out of p.mask .
