Did you actually run diff on the 1.2.1-r3 and 1.2.1-r4 versions of Mozilla --- /usr/portage/net-www/mozilla/mozilla-1.2.1-r3.ebuild Wed Dec 25 20:41:34 2002 +++ /usr/portage/net-www/mozilla/mozilla-1.2.1-r4.ebuild Thu Dec 26 15:14:40 2002 @@ -1,6 +1,6 @@ # Copyright 1999-2002 Gentoo Technologies, Inc. # Distributed under the terms of the GNU General Public License v2 -# $Header: /home/cvsroot/gentoo-x86/net-www/mozilla/mozilla-1.2.1-r3.ebuild,v 1.7 2002/12/26 01:41:34 azarah Exp $ +# $Header: /home/cvsroot/gentoo-x86/net-www/mozilla/mozilla-1.2.1-r4.ebuild,v 1.1 2002/12/26 20:14:40 azarah Exp $ IUSE="java crypt ipv6 gtk2 ssl ldap gnome" # Internal USE flags that I do not really want to advertise ... @@ -54,7 +54,7 @@ # mirror://gentoo/${P}-patches-${PATCH_VER}.tar.bz2" HOMEPAGE="http://www.mozilla.org" -KEYWORDS="~x86 ~ppc ~sparc ~alpha" +KEYWORDS="x86 ~ppc ~sparc ~alpha" SLOT="0" LICENSE="MPL-1.1 NPL-1.1" ONLY CHANGE IS THE KEYWORD FROM ~x86 to x86! WTF Azarah!?? You're making tons of people recompile it for that?! It's a pointless change!
this means making it stable !!! azarah: maybe carpaski could add a nice feature for this problem (i know there are just a few packages that are very extreme in sizing, but on a p3 500 it only takes about 5-15 minutes to compile)
Ok, sure, its not much of a change, but have a look at -r3's version number. It is already at 1.7, and was the whole time in testing. In general, I do not want to make changes to mozilla and such large packages, and then bump the version. But, now comes -r4 ... it is in stable profile, thus I assume: 1) Not everybody use testing packages, so it will be a recompile from 1.0.1 anyhow. 2) Many guys merge -r3 version 1.1, and this is not acceptible, as there did go in some fixes. 3) Rsync does some weird things some times, so rather make sure they merge a fixed version (yeah well, I have seen it with xfree :/) Thus, bumping it is very logical. It is a stable release, meaning prob more than 60% users will upgrade from moz 1.0.1, and will have to recompile anyhow. New bugs that come in, will be against -r4, so I will not have to wonder what CVS version of the ebuild it was. And lastly, if you really have an issue with this, have a look at the 'inject' option to emerge.
