I would like to use the speed tracer extension [1]. However it requires chromium being called with --enable-extension-timeline-api [2]. _1 http://code.google.com/webtoolkit/speedtracer _2 http://code.google.com/webtoolkit/speedtracer/get-started.html Per email I suggested the use of a useflag. However Pawel replied with: > I'd prefer to limit the number of different USE flags, to make testing > easier. However, I think Ubuntu or some other distro has some file in > /etc that makes it possible to customize chromium launch flags. I would still prefer a useflag. It seems to be the Gentoo way - Ubuntu does not have useflags so it is only natural that *they* make this configurable some other way. Also using some magic file would just make testing easier if you DID NOT test with that magic file being present. Of course to do that you could alternatively just not test with the timeline-api useflag set. Reproducible: Always Steps to Reproduce:
Copy /usr/share/applications/chromium-browser-chromium.desktop to your .local/share/applications and edit the command line in it to do what you want. No need to force a recompile of the whole thing for such a trivial change.
Useflags are the wrong place to control runtime behavior. Useflags are for compile-time changes (you really want to recompile to lock in some parameters?). Why not shell alias or adjust your DE's XDG configuration? alias chromm='nohup chromium-browser-live --enable-accelerated-2d-canvas --enable-extension-timeline-api --remote-debugging-port=1235 --user-data-dir=/home/ormaaj/.config/chromium &>/dev/null &'
(In reply to comment #2) > Useflags are the wrong place to control runtime behavior. That of course is a much better reason not to use a useflag than the ones originally given. > Why not shell alias or adjust your DE's XDG configuration? Well that's possible also. But since the ebuild maintainers asked for ideas from users some time ago I suggested something like this per email, which I think would have been the right place to discuss this. But they wanted a but report - here we go. I left out some details - this is just the pointer they seem to require. I don't feel strongly about this. In fact I am not going to use speedtracer for the time being. Just felt a bit guilty because I made the original request quite some time ago, and did not create the bug report as requested until now.
USE flag is not the right solution, there are just too many command-line flags. A file in /etc is fine, provided we're consistent with other distros like Debian or Ubuntu.
Adding something to /etc might be appropriate if you wanted a global configuration affecting all users. For persistent per-user flags I'd propose adding the option to about:flags upstream for consistency with the way other such options are set.
The latest versions of www-client/chromium (13.x and 9999) now provide an /etc/chromium/default file and also make it possibly to use CHROMIUM_USER_FLAGS env variable that overrides /etc/chromium/default settings (this is all based on Debian's launcher script). Enjoy!
(In reply to comment #6) > The latest versions of www-client/chromium (13.x and 9999) now provide an > /etc/chromium/default file and also make it possibly to use > CHROMIUM_USER_FLAGS env variable that overrides /etc/chromium/default > settings (this is all based on Debian's launcher script). > > Enjoy! Great! Thanks :)
