On Sat, 23 Jul 2005, Holly Bostick wrote:
I've gotta say, I'm getting tired of upgrading them (I saw the upgrade to 1.0.6 two days ago, but waited; there was an upgrade to 1.0.6-r1, which I took yesterday afternoon, and today I have to upgrade to 1.0.6-r2).
I'm getting tired of it too. I would understand this upgrade cycle with some smaller packages, but ff and tb are huge programs to compile this often.
And as if bumping the revisions were not enough they keep deleting the previous versions from the tree making it hard to mask the new ones: If the old one is gone, you just cannot add the new one to your package.mask file - you also have to put a "fake" ebuild to your local portage tree. Otherwise portage will want to *downgrade* with emerge -u world. Or worse, complain about missing packages if the current one is the only one in the tree, as it was with firefox-1.0.5-r1.
In any case, I'm not having any problems with firefox or tbird 1.0.6-r1
That's the real paradox here. I don't remember when was the last time I had a problem with ff (actually I use only Galeon these days, compiled against ff) so it feels so stupid to compile it just because of these revision bumps (yeah, I know - you don't *have to* upgrade, they'll say - but then again, read what I said above).
I was going to post a question as to whether anybody knew how many more revisions we're going to see to the Mozilla programs in the next couple days; I understand heavy development, but three upgrades in three days is a bit much even for me (since it takes an hour and a half or so to compile each program, and further means I have to use Konq for that time if I don't want to mess up ff by having it loaded while it's upgrading.
Hmmm... I don't see how it could mess ff this way.
So I'd love to know if this is likely to settle down soon, if anybody happens to follow the relevant development.
Relevant? But is it really...? ;-) -- T.G. -- gentoo-user@gentoo.org mailing list
