aszlig f28b71023c chromium/updater: Don't import <nixpkgs> again ... This effectively resets the attributes given at the point the main <nixpkgs> is imported and thus for example is also reading in stuff like ~/.nixpkgs/config.nix again, which might lead to unexpected results. We now only import <nixpkgs> now if the updater is auto-called (like in update.sh), otherwise the required attributes are passed by callPackage within the Chromium scope. I remember noting about this a while ago either on IRC or on GitHub, but I can't find it right now, so thanks to @obadz for reminding me about this in #15225. Tested this by running the updater and also using: NIXPKGS_CONFIG=$(pwd)/broken.nix nix-instantiate --arg config {} -A chromium The contents of broken.nix were: EVALERR{ Signed-off-by: aszlig <aszlig@redmoonstudios.org> Fixes: #15225		2016-05-04 22:35:24 +02:00
..
patches	chromium/source: Move patches into its own subdir	2016-03-20 16:44:34 +01:00
browser.nix	Do some large, concurrency-capable builds on dedicated machines	2016-05-04 18:16:27 +02:00
common.nix	Merge 'staging' into closure-size	2016-04-07 14:40:51 +02:00
default.nix	chromium/updater: Don't import <nixpkgs> again	2016-05-04 22:35:24 +02:00
plugins.nix	replace makeSearchPath tree-wise to take care of possible multiple outputs	2016-04-13 22:09:41 +03:00
update.nix	chromium/updater: Don't import <nixpkgs> again	2016-05-04 22:35:24 +02:00
update.sh	chromium/source: Move update.nix to parent dir	2016-03-20 16:53:08 +01:00
upstream-info.nix	chromium: Update all channels to latest versions	2016-03-30 15:24:39 +02:00