mozilla-1.6a should in fact be mozilla-1.6_alpha, because as we well know, 1.6a > 1.6 > 1.6_beta > 1.6_alpha, and the mozilla-1.6a in portage is really mozilla-1.6_alpha (there is no mozilla 1.6 out yet). Related to the problem in question is the fact that I cannot get the meaning of the following code in the mozilla.ebuild: # handle _rc versions MY_PV1="${PV/_}" MY_PV2="${MY_PV1/eta}" I think something like the following would make more sense: case $PV in *_alpha) MY_PV1="${PV/_alpha/a}" ;; *_beta) MY_PV1="${PV/_beta/b}" ;; *_rc[0-9]*) MY_PV1="${PV/_rc/rc}" ;; *) MY_PV1="${PV}" ;; esac SRC_URI="mirror://mozilla/${PN}/releases/${PN}${MY_PV1}/src/${PN}-source-${MY_PV1}.tar.bz2" Should these be two separate bugreports?
I got it. MY_PV1="${PV/_}" MY_PV2="${MY_PV1/eta}" is supposed to make _beta -> b Still, I think it makes more sense to include the cases when we have _alpha and _rc versions, since this is the problem we're facing right now.
Can I get some attention here? There is now a mozilla-1.6b.ebuild, and I'm really curious how people are going to "upgrade" when mozilla-1.6 finally hits portage. It is not too late to remove thouse 1.6a and 1.6b ebuilds and name them properly as 1.6_alpha and 1.6_beta.
I'm looking into it. This will be corrected before 1.6 release.
Ebuilds renamed, should be fixed. Will deal with the case statement later - do me a favor and file a new bug on it? Thanks much
Bug 36213 has been added to the database
