Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use chromium release channels #36

Merged
merged 5 commits into from Jul 4, 2012
Merged

Conversation

aszlig
Copy link
Member

@aszlig aszlig commented Jul 4, 2012

Allow to configure the chromium release channel (stable, beta, dev) and alter the update script to fetch sha hashes of all current releases.

The previos update script just used the last version of chromium that showed up
at the bucket list at:

http://commondatastorage.googleapis.com/chromium-browser-official/

I'm not sure which channel this list actually holds, so I'm going to switch now
using the official release channels grabbed by omahaproxy. This also has the
advantage that we can provide different versions/flavors of chromium.

We now also write our data to sources.nix instead of source.nix, as we have more
than one source.
This means that we now have hashes and URLs for the latest versions of chromium
and can now work on integrating the changes into default.nix.
Switch to channel based sources and default to the "stable" channel.
The current stable version won't build if gyp can't use svnversion from the
subversion package, so let's provide it for versions below 21.x.
As already promised, the old single-channel source.nix is now obsolete as we're
using Omahaproxy now and the build of the stable version finishes successful and
the browser runs fine.
shlevy added a commit that referenced this pull request Jul 4, 2012
@shlevy shlevy merged commit 6ba310e into NixOS:master Jul 4, 2012
ethancedwards8 pushed a commit to ethancedwards8/nixpkgs that referenced this pull request Apr 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants