Gawain Lynch wrote:
For those of us that want to use Firefox 2 to browse on FC6 without having to rebuild half of the system, I have *hacked* up a quick solution that allows a parallel install of FF2 along side FC6's 1.5x.
I've tried the brandnew Firefox 2.0 Release parallel to 1.5.0.7 from:
http://releases.mozilla.org/pub/mozilla.org/firefox/releases/2.0/
Very fast rendering with the 2.0 version. Faster as with Fedora 1.5.0.7-7.fc6. Resizing windows and web rendering is wonderful faaaaast.
We need it in Fedora-Extras soon!
Best regards, Marcus
On Mon, Oct 23, 2006 at 07:29:01PM +0200, Marcus Hartig wrote:
http://releases.mozilla.org/pub/mozilla.org/firefox/releases/2.0/ Very fast rendering with the 2.0 version. Faster as with Fedora 1.5.0.7-7.fc6. Resizing windows and web rendering is wonderful faaaaast.
Have you compared the speed with a pango-disabled build of 1.5.0.7?
Marcus Hartig wrote:
Gawain Lynch wrote:
For those of us that want to use Firefox 2 to browse on FC6 without having to rebuild half of the system, I have *hacked* up a quick solution that allows a parallel install of FF2 along side FC6's 1.5x.
I've tried the brandnew Firefox 2.0 Release parallel to 1.5.0.7 from:
http://releases.mozilla.org/pub/mozilla.org/firefox/releases/2.0/
Very fast rendering with the 2.0 version. Faster as with Fedora 1.5.0.7-7.fc6. Resizing windows and web rendering is wonderful faaaaast.
The upstream builds disable a few key features that we enable, and they do a static build instead of linking everything dynamically. Comparing Fedora builds to upstream builds is not fair at all. Besides, I've run the two. It's not really that much faster. The overhead in the Fedora packages is primarily because we install a bunch of langpacks.
On Mon, Oct 23, 2006 at 02:59:26PM -0400, Christopher Aillon wrote:
Marcus Hartig wrote:
Gawain Lynch wrote:
For those of us that want to use Firefox 2 to browse on FC6 without having to rebuild half of the system, I have *hacked* up a quick solution that allows a parallel install of FF2 along side FC6's 1.5x.
I've tried the brandnew Firefox 2.0 Release parallel to 1.5.0.7 from:
http://releases.mozilla.org/pub/mozilla.org/firefox/releases/2.0/
Very fast rendering with the 2.0 version. Faster as with Fedora 1.5.0.7-7.fc6. Resizing windows and web rendering is wonderful faaaaast.
The upstream builds disable a few key features that we enable, and they do a static build instead of linking everything dynamically. Comparing Fedora builds to upstream builds is not fair at all. Besides, I've run the two. It's not really that much faster. The overhead in the Fedora packages is primarily because we install a bunch of langpacks.
Well, i tried this 2.0 version and found 2.0 does not use all cpu power when several animated images are in a webpage as in the 1.5 case (see reports from a couple of weeks ago). I'll created bugzilla 211904.
-Marcel
Christopher Aillon wrote:
Marcus Hartig wrote:
Gawain Lynch wrote:
For those of us that want to use Firefox 2 to browse on FC6 without having to rebuild half of the system, I have *hacked* up a quick solution that allows a parallel install of FF2 along side FC6's 1.5x.
I've tried the brandnew Firefox 2.0 Release parallel to 1.5.0.7 from:
http://releases.mozilla.org/pub/mozilla.org/firefox/releases/2.0/
Very fast rendering with the 2.0 version. Faster as with Fedora 1.5.0.7-7.fc6. Resizing windows and web rendering is wonderful faaaaast.
The upstream builds disable a few key features that we enable, and they do a static build instead of linking everything dynamically. Comparing Fedora builds to upstream builds is not fair at all. Besides, I've run the two. It's not really that much faster. The overhead in the Fedora packages is primarily because we install a bunch of langpacks.
Would it possible not to install all the different language packages when I just want just one?
Rahul
Le Lun 23 octobre 2006 22:47, Rahul Sundaram a écrit :
Would it possible not to install all the different language packages when I just want just one?
Even if the langpacks were split I guess the firefox group would do like the xorg one - install all by default just to be sure they're present at the right time. (No english-only by default is not ok for basic non-us users)
On 10/24/06, Nicolas Mailhot nicolas.mailhot@laposte.net wrote:
Le Lun 23 octobre 2006 22:47, Rahul Sundaram a écrit :
Would it possible not to install all the different language packages when I just want just one?
Even if the langpacks were split I guess the firefox group would do like the xorg one - install all by default just to be sure they're present at the right time. (No english-only by default is not ok for basic non-us users)
Can't they just be part of the various language install options during installation? People who don't customize and tick the box for their language will end up with US english for almost everything anyway.
n0dalus.
Le Mer 25 octobre 2006 03:44, n0dalus a écrit :
On 10/24/06, Nicolas Mailhot nicolas.mailhot@laposte.net wrote:
Le Lun 23 octobre 2006 22:47, Rahul Sundaram a écrit :
Would it possible not to install all the different language packages when I just want just one?
Even if the langpacks were split I guess the firefox group would do like the xorg one - install all by default just to be sure they're present at the right time. (No english-only by default is not ok for basic non-us users)
Can't they just be part of the various language install options during installation? People who don't customize and tick the box for their language will end up with US english for almost everything anyway.
Having a major desktop app like firefox not localized by default would be a big problem. So far no one proposed any solution robust wrt : - non-technical users - upgrades
The "right" solution would probably consist of a mix of : - dumping in /etc a file declaring which languages should be supported by the system at the UI level, including fallback order (app translations, man pages and other localised documentation...) - dumping in /etc a file declaring which languages should be supported by the system at the view/edit level (fonts, spellcheckers...) - writing a system-config-foo to edit those files - integrating this UI in anaconda for initial install - tagging package content which falls in one of the two categories (either at rpm or at comps level - IMHO the right place is rpm, the easier to do is comps) - have yum/rpm respect the language filtering
This is major work and so far just installing everything has proved easier. The problem is known since before FC was born.
Regards,
O/H Nicolas Mailhot έγραψε:
Le Mer 25 octobre 2006 03:44, n0dalus a écrit :
On 10/24/06, Nicolas Mailhot nicolas.mailhot@laposte.net wrote:
Le Lun 23 octobre 2006 22:47, Rahul Sundaram a écrit :
Would it possible not to install all the different language packages when I just want just one?
Even if the langpacks were split I guess the firefox group would do like the xorg one - install all by default just to be sure they're present at the right time. (No english-only by default is not ok for basic non-us users)
Can't they just be part of the various language install options during installation? People who don't customize and tick the box for their language will end up with US english for almost everything anyway.
Having a major desktop app like firefox not localized by default would be a big problem. So far no one proposed any solution robust wrt :
- non-technical users
- upgrades
The "right" solution would probably consist of a mix of :
- dumping in /etc a file declaring which languages should be supported by
the system at the UI level, including fallback order (app translations, man pages and other localised documentation...)
- dumping in /etc a file declaring which languages should be supported by
the system at the view/edit level (fonts, spellcheckers...)
- writing a system-config-foo to edit those files
- integrating this UI in anaconda for initial install
- tagging package content which falls in one of the two categories (either
at rpm or at comps level - IMHO the right place is rpm, the easier to do is comps)
- have yum/rpm respect the language filtering
This is major work and so far just installing everything has proved easier. The problem is known since before FC was born.
Nicholas, these are very interesting ideas and it would be a shame for them to get burried in the list's archive. I don't know what the overhead/gain would be, but couldn't something like this also potentially save us space in the ISOs?
Maybe it would be a good idea to put these kind of opinions/brainstormings on the wiki page à la live.gnome. Much better for future reference than list archives.
-d
Le dimanche 29 octobre 2006 à 13:23 +0000, Dimitris Glezos a écrit :
O/H Nicolas Mailhot έγραψε:
The "right" solution would probably consist of a mix of :
...
This is major work and so far just installing everything has proved easier. The problem is known since before FC was born.
Nicholas, these are very interesting ideas and it would be a shame for them to get burried in the list's archive. I don't know what the overhead/gain would be, but couldn't something like this also potentially save us space in the ISOs?
I doubt it, you'd win more by teaching apps to use the same spellcheckers format & files
Maybe it would be a good idea to put these kind of opinions/brainstormings on the wiki page à la live.gnome. Much better for future reference than list archives.
Feel free to put/copy/adapt it in the wiki if you want. Though IMHO it's highly unlikely people will invest in such a deep change just to save a few bytes on disk (maybe if it impacts OLPC…)
Regards,
-
Christopher Aillon -
Dimitris Glezos -
Marcel J.E. Mol -
Marcus Hartig -
Matthew Miller -
n0dalus -
Nicolas Mailhot -
Rahul Sundaram