aboutsummaryrefslogtreecommitdiff
path: root/scripts/generate-patches.pl.in
AgeCommit message (Collapse)Author
2010-11-29* Move the patch generator into a module.Eelco Dolstra
2010-11-29* Don't generate patches if the system type differs.Eelco Dolstra
2010-11-29* Impose a configurable time limit on patch generation. This isEelco Dolstra
necessary because bsdiff has some pathological worst-case behaviour, e.g. O(n^2) on files consisting only of 0s.
2010-07-21* Don't barf if the source NAR for a patch has disappeared.Eelco Dolstra
2010-06-23* Ignore packages that don't have a version.Eelco Dolstra
* Work on a manifest instead of a channel directory.
2007-03-30* Make the maximum patch size configurable.Eelco Dolstra
2007-01-23* New kind of manifest object: "localPath", which denotes that a storeEelco Dolstra
path can be created by copying it from another location in the file system. This is useful in the NixOS installation.
2007-01-23* Successors have been gone for ages.Eelco Dolstra
2007-01-08* Reject patches that are larger than a certain fraction of the full archiveEelco Dolstra
(currently 60%). Large patches aren't very economical.
2007-01-08* Huge speedup in patch propagation (20 minutes or so to 3 seconds).Eelco Dolstra
2006-10-12* Reduce the maximum archive size for patch generation to 100 MB toEelco Dolstra
prevent trashing on nix.cs.uu.nl.
2006-10-04* tmpnam() -> File::Temp::tempdir().Eelco Dolstra
2005-12-13* Change `referer' to `referrer' throughout. In particular, theEelco Dolstra
nix-store query options `--referer' and `--referer-closure' have been changed to `--referrer' and `--referrer-closure' (but the old ones are still accepted for compatibility).
2005-06-18* Don't create patches for archives >= 150 MB because bsdiff can'tEelco Dolstra
handle it. It crashed on the 234 MB tetex archive. Probably we will never be able to handle archives of that size on 32-bit machines (because bsdiff does everything in memory requiring max(17*n,9*n+m)+O(1) bytes, so the address space simply isn't there).
2005-04-12* Damn. Disable the USE heuristic for now, since the deriver in theEelco Dolstra
database isn't always in the manifest (so the reference graph cannot be reconstructed fully).
2005-03-18* Ignore hash conflicts in gc-releases.pl.Eelco Dolstra
2005-03-15* Use SHA-256 for nix-push.Eelco Dolstra
2005-03-14* Prefix hash algorithm in patch generator too.Eelco Dolstra
2005-03-01* Use a weighted use heuristic to disambiguate between multipleEelco Dolstra
occurances of a component. If the shortest path distance between a component P and Q in the referers graph is D, then the contribution of Q to the use of P is 1 / R^D, where R >= 1, typically 2. This expresses that distant indirect uses are less important than nearby uses. For instance, this can disambiguate between the bootstrap GCC in Nixpkgs and the GCC of the final stdenv (the former has more uses, but they are further away), and between the GCC of the final stdenv and the GCC+G77 build (the latter has very few uses).
2005-02-28* Added a disambiguation heuristic: if two components have the sameEelco Dolstra
name but differ to much in sice (by more than a factor of 3), then never generate a patch.
2005-02-24* Properly specify the hash algorithm in the manifests, and read itEelco Dolstra
too. * Change the default hash for nix-prefetch-url back to md5, since that's what we use in Nixpkgs (for now; a birthday attack is rather unlikely there).
2005-02-01* Get rid of hardcoded paths.Eelco Dolstra