This is Gentoo's testing wiki. It is a non-operational environment and its textual content is outdated.
Please visit our production wiki at https://wiki.gentoo.org
Project:Chromium
| Chromium in Gentoo Project | |
|---|---|
| Description | The Chromium in Gentoo project manages the Chromium-related ebuilds within Gentoo. |
| Project email | chromium@gentoo.org |
| Lead(s) |
No lead election date set |
| Member(s) |
|
| Subproject(s) (and inherited member(s)) |
(none) |
| Parent Project | Gentoo |
| Project listing | |
Goals
- Ensure that Chromium-related ebuilds are kept up to date and well integrated with the rest of the Gentoo system
- Build a community of Gentoo users interested in Chromium development and packaging efforts (testing, bug fixing, feedback)
- Make Gentoo the best and most friendly platform for Chromium development
Recruitment
We are currently looking for users interested in helping the project with one or more jobs.
To learn more, visit the Staffing Needs page.
Resources
Resources offered by the chromium project are:
- Source tarballs for Chromium and V8
- Nacl patches and build scripts
- V8 API changes
- Current releases by platform and channel
Frequently asked questions
What is the difference between Google Chrome and Chromium?
See differences between Google Chrome and Linux distro Chromium.
Why are dev channel releases hard masked?
Dev channel releases are for developers and people who want more experimental features and accept more unstable software. It also allows you to choose the channel you want to be on (dev = hard masked, beta = ~arch, stable = arch).
Aren't dev channel releases just weekly snapshots?
No, each release goes through QA first. It's not uncommon to delay a release because of increased crashiness or other instability.
Where can I find more info about the releases?
You can also follow Google Chrome releases blog.
Where can I find more info about the upstream package, system integration issues, etc?
See Linux technical FAQ.
No, actually it is a result of using system version of ffmpeg instead of the bundled one.
The browser fails to compile with an error like "fatal error: libavcore/samplefmt.h: No such file or directory"
Are you using media-video/ffmpeg-9999? Try downgrading ffmpeg. Sometimes the project makes incompatible changes and the projects using the library take some time to adjust.
Useful bug queries
- chromium security bugs
- chromium bugs
- chromium bugs (Herd Testers' help wanted)
- chromium upstream bugs mentioning Gentoo
Herd testers' corner
How to become a herd tester?
You can just start contributing, see bug queries above, especially the one for Herd Testers. Frequently project members ask for help with reproducing issues, or testing fixes, or just any helpful comments. Feel free to ask for more details on the project mail alias, see recruitment.
What benefits do I get as a Herd Tester?
If you become an official herd tester, you can get more privileges on Gentoo Bugzilla, and also a special badge on Gentoo Forums. To gain those privileges, you have to pass the ebuild quiz.
Chromium in Gentoo project appreciates all contributions and always gives credit where credit is due. You do not have to pass any quizzes to get recognized.
Who are the official herd testers?
| Name | Nickname |
|---|---|
| Julien Sanchez | julien.sanchez |