about summary refs log tree commit diff
path: root/corepkgs/Makefile.am
AgeCommit message (Collapse)AuthorFilesLines
2012-07-25 import: If the path is a valid .drv file, parse it and generate a derivation ↵Shea Levy1-1/+2
attrset. The generated attrset has drvPath and outPath with the right string context, type 'derivation', outputName with the right name, all with a list of outputs, and an attribute for each output. I see three uses for this (though certainly there may be more): * Using derivations generated by something besides nix-instantiate (e.g. guix) * Allowing packages provided by channels to be used in nix expressions. If a channel installed a valid deriver for each package it provides into the store, then those could be imported and used as dependencies or installed in environment.systemPackages, for example. * Enable hydra to be consistent in how it treats inputs that are outputs of another build. Right now, if an input is passed as an argument to the job, it is passed as a derivation, but if it is accessed via NIX_PATH (i.e. through the <> syntax), then it is a path that can be imported. This is problematic because the build being depended upon may have been built with non-obvious arguments passed to its jobset file. With this feature, hydra can just set the name of that input to the path to its drv file in NIX_PATH
2012-07-09 Inline fetchurl.shEelco Dolstra1-1/+1
2012-07-09 corepkgs: distribute fetchurl filesShea Levy1-1/+1
2012-01-03 * Move the implementation of the ‘derivation’ primop into a separateEelco Dolstra1-1/+1
file.
2012-01-03 * Add a test for nix-channel.Eelco Dolstra1-4/+4
* Refactor the nix-channel unpacker a bit.
2012-01-03 * Refactoring: Get rid of a few subdirectories in corepkgs/, and someEelco Dolstra1-1/+11
other simplifications. * Use <nix/...> to locate the corepkgs. This allows them to be overriden through $NIX_PATH. * Use bash's pipefail option in the NAR builder so that we don't need to create a temporary file.
2005-04-07 * Get rid of fetchurl, we don't need it anymore.Eelco Dolstra1-1/+1
2004-12-20 * Place manifests in /nix/var/nix/manifests.Eelco Dolstra1-1/+1
* Use the new patch downloader.
2004-06-21 * Adapted nix-pull to use the new substitute mechanism.Eelco Dolstra1-1/+1
2004-04-21 * Channels. These allow you to stay current with an evolving set ofEelco Dolstra1-1/+1
Nix expressions. To subscribe to a channel (needs to be done only once): nix-channel --add \ http://catamaran.labs.cs.uu.nl/dist/nix/channels/nixpkgs-unstable This just adds the given URL to ~/.nix-channels (which can also be edited manually). To update from all channels: nix-channel --update This fetches the latest expressions and pulls cache manifests. The default Nix expression (~/.nix-defexpr) is made to point to the conjunction of the expressions downloaded from all channels. So to update all installed derivations in the current user environment: nix-channel --update nix-env --upgrade '*' If you are really courageous, you can put this in a cronjob or something. You can subscribe to multiple channels. It is not entirely clear what happens when there are name clashes between derivations from different channels. From nix-env/main.cc it appears that the one with the lowest (highest?) hash will be used, which is pretty meaningless.
2003-11-22 * Don't use a hard-coded path.Eelco Dolstra1-1/+1
2003-07-18 * Generate nar.sh, fetchurl.sh.Eelco Dolstra1-10/+1
2003-07-10 * The policy-free derivate sharing now *almost* works. :-) For anyEelco Dolstra1-0/+2
hash for which no local expansion is available, Nix can execute a `substitute' which should produce a path with such a hash. This is policy-free since Nix does not in any way specify how the substitute should work, i.e., it's an arbitrary (unnormalised) fstate expression. For example, `nix-pull' registers substitutes that fetch Nix archives from the network (through `wget') and unpack them, but any other method is possible as well. This is an improvement over the old Nix sharing scheme, which had a policy (fetching through `wget') built in. The sharing scheme doesn't work completely yet because successors from fstate rewriting have to be registered on the receiving side. Probably the whole successor stuff can be folded up into the substitute mechanism; this would be a nice simplification.
2003-07-10 * Get `nix-push' working again. It now uses Nix/Fix to create NixEelco Dolstra1-0/+8
archives (using the package in corepkgs/nar). * queryPathByHash -> expandHash, and it takes an argument specifying the target path (which may be empty). * Install the core Fix packages in $prefix/share/fix. TODO: bootstrap Nix and install Nix as a Fix package.