Eelco Dolstra
92e832348d
* Lots of manual stuff. Reference pages for most Nix commands.
...
* nix-pull now requires the full url to the manifest, i.e.,
`/MANIFEST/' is no longer automatically appended.
* nix-prefetch-url works again.
2004-02-10 16:14:47 +00:00
Eelco Dolstra
9a404e45c9
* Synchronous nix-pull' with nix-push'.
...
* Use curl instead of wget.
2004-01-14 14:20:33 +00:00
Eelco Dolstra
16f9b133ec
* Improved `nix-push': it now uses HTTP PUT (instead of rsync) to copy
...
files. Target location is no longer hard-coded; it accepts a number
of URLs on the command line.
* `nix-install-package': compatibility fixes.
2004-01-14 11:13:08 +00:00
Eelco Dolstra
397c8ba898
* Missing semicolons.
2003-12-21 21:56:54 +00:00
Eelco Dolstra
a3ca74a1c3
* Bug fix in nix-push.
2003-12-01 16:34:35 +00:00
Eelco Dolstra
5d2b424804
* Use a system name that does not include the OS manufacturer (i.e.,
...
"i686-linux" instead of "i686-suse-linux").
2003-12-01 14:36:50 +00:00
Eelco Dolstra
9486dda115
* Fix nix-push.
2003-11-22 20:39:51 +00:00
Eelco Dolstra
0eab306466
* NarPath -> NarName.
2003-10-20 09:08:44 +00:00
Eelco Dolstra
ab5e8767fa
* Get nix-push to work again.
...
* Fixed svn:ignore on externals/.
2003-10-16 13:13:39 +00:00
Eelco Dolstra
5d4171f7fb
* Synchronise terminology with the ICSE paper (e.g., slice -> closure,
...
fstate -> Nix expression).
* Fix src/test.cc.
2003-10-07 12:27:49 +00:00
Eelco Dolstra
c4f1f49574
* nix-push generated invalid (old-style) slices.
...
* nar.sh needs a path.
2003-08-28 10:10:12 +00:00
Eelco Dolstra
b9c9b461ea
* Made nix-push much faster.
2003-08-05 12:30:06 +00:00
Eelco Dolstra
a01629894d
* Use `--query --requisites' and include successors when pushing. Don't
...
use `--query --generators' anymore.
2003-07-29 15:19:03 +00:00
Eelco Dolstra
c7bdb76fe4
* Syntax fixes.
...
* When pushing, put the hash in the file name so that the
client can verify (proof-carrying file names?).
2003-07-21 21:34:56 +00:00
Eelco Dolstra
54664b6fb7
* The write() system call can write less than the requested
...
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 21:24:02 +00:00
Eelco Dolstra
9d56ca219f
* Substitute fixes.
2003-07-16 20:00:51 +00:00
Eelco Dolstra
9c620e4afa
* Generate the scripts so that we can substitute the prefix
...
etc. correctly.
* Fixed nix-switch.
2003-07-13 18:58:03 +00:00
