Summary: | Stupid Mozilla release. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Doug Goldstein (RETIRED) <cardoe> |
Component: | New packages | Assignee: | Martin Schlemmer (RETIRED) <azarah> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | mholzer |
Priority: | High | ||
Version: | 1.4_rc1 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Doug Goldstein (RETIRED)
2003-01-04 16:40:11 UTC
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. |