about summary refs log tree commit diff
path: root/scripts/nix-push.in
AgeCommit message (Collapse)AuthorFilesLines
2005-01-25 * Really fix the substitute mechanism, i.e., ensure the closureEelco Dolstra1-30/+87
invariant by registering references through the manifest. * Added a test for nix-pull.
2005-01-19 * Set the Perl search path properly (reported by Roy van den Broek).Eelco Dolstra1-1/+1
2004-12-28 * Added a function to write manifests.Eelco Dolstra1-26/+29
2004-12-13 * Include the size of the bzipped archive (necessary for computing theEelco Dolstra1-5/+15
cheapest download path), as well as the hash of the contents of the path (necessary for checking patch applicability).
2004-08-20 * Setuid support for sharing a Nix installation between multipleEelco Dolstra1-1/+1
users. If the configure flag `--enable-setuid' is used, the Nix programs nix-env, nix-store, etc. are installed with the setuid bit turned on so that they are executed as the user and group specified by `--with-nix-user=USER' and `--with-nix-group=GROUP', respectively (with defaults `nix' and `nix'). The setuid programs drop all special privileges if they are executed by a user who is not a member of the Nix group. The setuid feature is a quick hack to enable sharing of a Nix installation between users who trust each other. It is not generally secure, since any user in the Nix group can modify (by building an appropriate derivation) any object in the store, and for instance inject trojans into binaries used by other users. The setuid programs are owned by root, not the Nix user. This is because on Unix normal users cannot change the real uid, only the effective uid. Many programs don't work properly when the real uid differs from the effective uid. For instance, Perl will turn on taint mode. However, the setuid programs drop all root privileges immediately, changing all uids and gids to the Nix user and group.
2004-04-21 * Channels. These allow you to stay current with an evolving set ofEelco Dolstra1-1/+3
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.
2004-04-15 * Allow extra parameters to be passed to Curl through the `CURL_FLAGS'Eelco Dolstra1-1/+1
environment variable. This is useful for passing authentication information (it won't show up in `ps'). Hacky - nix-push should abstract over the use of Curl.
2004-04-06 * Switched from wget to curl.Eelco Dolstra1-7/+7
* Made the dependencies on bzip2 and the shell explicit.
2004-03-15 * Make perl a dependency of Nix.Eelco Dolstra1-1/+1
2004-02-13 * Only include predecessors that are themselves being pushed.Eelco Dolstra1-1/+6
Otherwise the substitute mechanism can break in subtle ways.
2004-02-10 * Lots of manual stuff. Reference pages for most Nix commands.Eelco Dolstra1-1/+1
* nix-pull now requires the full url to the manifest, i.e., `/MANIFEST/' is no longer automatically appended. * nix-prefetch-url works again.
2004-01-14 * Synchronous `nix-pull' with `nix-push'.Eelco Dolstra1-1/+1
* Use curl instead of wget.
2004-01-14 * Improved `nix-push': it now uses HTTP PUT (instead of rsync) to copyEelco Dolstra1-42/+77
files. Target location is no longer hard-coded; it accepts a number of URLs on the command line. * `nix-install-package': compatibility fixes.
2003-12-21 * Missing semicolons.Eelco Dolstra1-1/+1
2003-12-01 * Bug fix in nix-push.Eelco Dolstra1-19/+19
2003-12-01 * Use a system name that does not include the OS manufacturer (i.e.,Eelco Dolstra1-1/+1
"i686-linux" instead of "i686-suse-linux").
2003-11-22 * Fix nix-push.Eelco Dolstra1-36/+32
2003-10-20 * NarPath -> NarName.Eelco Dolstra1-1/+1
2003-10-16 * Get nix-push to work again.Eelco Dolstra1-32/+78
* Fixed svn:ignore on externals/.
2003-10-07 * Synchronise terminology with the ICSE paper (e.g., slice -> closure,Eelco Dolstra1-2/+2
fstate -> Nix expression). * Fix src/test.cc.
2003-08-28 * nix-push generated invalid (old-style) slices.Eelco Dolstra1-1/+1
* nar.sh needs a path.
2003-08-05 * Made nix-push much faster.Eelco Dolstra1-18/+33
2003-07-29 * Use `--query --requisites' and include successors when pushing. Don't Eelco Dolstra1-8/+8
use `--query --generators' anymore.
2003-07-21 * Syntax fixes.Eelco Dolstra1-10/+20
* When pushing, put the hash in the file name so that the client can verify (proof-carrying file names?).
2003-07-16 * The write() system call can write less than the requested Eelco Dolstra1-0/+4
number of bytes, e.g., in case of a signal like SIGSTOP. This caused `nix --dump' to fail sometimes. Note that this bug went unnoticed because the call to `nix --dump' is in a pipeline, and the shell ignores non-zero exit codes from all but the last element in the pipeline. Is there any way to check the result of the initial elements in the pipeline? (In other words, is it at all possible to write reliable shell scripts?)
2003-07-16 * Substitute fixes.Eelco Dolstra1-14/+11
2003-07-13 * Generate the scripts so that we can substitute the prefixEelco Dolstra1-0/+70
etc. correctly. * Fixed nix-switch.