* Unify the treatment of sources copied to the store, and recursive
SHA-256 outputs of fixed-output derivations.  I.e. they now produce
  the same store path:
  $ nix-store --add x
  /nix/store/j2fq9qxvvxgqymvpszhs773ncci45xsj-x
  $ nix-store --add-fixed --recursive sha256 x
  /nix/store/j2fq9qxvvxgqymvpszhs773ncci45xsj-x
  the latter being the same as the path that a derivation
    derivation {
      name = "x";
      outputHashAlgo = "sha256";
      outputHashMode = "recursive";
      outputHash = "...";
      ...
    };
  produces.
  This does change the output path for such fixed-output derivations.
  Fortunately they are quite rare.  The most common use is fetchsvn
  calls with SHA-256 hashes.  (There are a handful of those is
  Nixpkgs, mostly unstable development packages.)
  
* Documented the computation of store paths (in store-api.cc).
			
			
This commit is contained in:
		
							parent
							
								
									09bc0c502c
								
							
						
					
					
						commit
						64519cfd65
					
				
					 12 changed files with 191 additions and 79 deletions
				
			
		|  | @ -290,7 +290,7 @@ static void performOp(unsigned int clientVersion, | |||
|     case wopAddToStore: { | ||||
|         /* !!! uberquick hack */ | ||||
|         string baseName = readString(from); | ||||
|         bool fixed = readInt(from) == 1; | ||||
|         readInt(from); /* obsolete; was `fixed' flag */ | ||||
|         bool recursive = readInt(from) == 1; | ||||
|         string hashAlgo = readString(from); | ||||
|          | ||||
|  | @ -300,7 +300,7 @@ static void performOp(unsigned int clientVersion, | |||
|         restorePath(tmp2, from); | ||||
| 
 | ||||
|         startWork(); | ||||
|         Path path = store->addToStore(tmp2, fixed, recursive, hashAlgo); | ||||
|         Path path = store->addToStore(tmp2, recursive, hashAlgo); | ||||
|         stopWork(); | ||||
|          | ||||
|         writeString(path, to); | ||||
|  |  | |||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue