Chromium packages update

[spot]

(Wow, has it really been June since I posted last

Comments

Just a thanks

[anonymous]

Many thanks for your work on this. It's great that there's now a 64 bit build, easy to install, for Fedora users.

Rawhide?

[anonymous]

Will you make a version for rawhide as well?

Re: Rawhide?

[spot]

Possibly, although the F-11 builds work fine on Rawhide now.

Re: Rawhide?

[ext_30795]

They stopped working. Bug-buddy is both required by you build and obsoleted by ABRT. This is something yum cannot fix.

Re: Rawhide?

[spot]

I'll have to look into this in more detail next week, there are a few ways we can fix this.

[figvam]

How often are the packages updated?

[spot]

A few times a week. I can't really automate the builds, because the code base is in such a state of flux that the patches need to be regularly rebased.

Command Line Option Issue

[anonymous]

User scripts don't work in this build until you tweak the command line options, the actual options of the .desktop file are:
chromium-browser --enable-plugins --enable-extensions --enable-greasemonkey

However "--enable-greasemonkey" seems to be outdated, I had to launch it with "--enable-user-scripts" to get user scripts working, that should really be changed.

chromium x86_64 builds looks under /usr/lib/mozilla/plugins path

[ext_204674]

I noticed that chromium-4.0.202.0-0.1.20090818svn23628.fc11.x86_64 looks under /usr/lib/mozilla/plugins for plugins:
strings /usr/lib64/chromium-browser/chromium-browser | grep '/usr/lib/'
/usr/lib/mozilla/plugins
besides looking under /usr/lib64/chromium/plugins/

On multilib Linux distributions, I think searching /usr/lib64/chromium/plugins then /usr/lib64/mozilla/plugins would make more sense.