about summary refs log tree commit diff
path: root/src
AgeCommit message (Collapse)AuthorFilesLines
2004-10-26 * Don't use ATmake / ATmatch anymore, nor the ATMatcher class.Eelco Dolstra11-304/+410
Instead we generate data bindings (build and match functions) for the constructors specified in `constructors.def'. In particular this removes the conversions between AFuns and strings, and Nix expression evaluation now seems 3 to 4 times faster.
2004-10-26 * Evaluate argument to `import'.Eelco Dolstra1-1/+2
2004-10-26 * Doh!Eelco Dolstra1-1/+1
2004-10-26 * String/path concatenation operator (`+').Eelco Dolstra5-5/+38
2004-10-26 * Mode `--parse-only' to parse the input (on stdin, `-'), and printEelco Dolstra1-8/+28
out the AST as an ATerm. * Mode `--eval-only' to parse and evaluate the input, and print the resulting normal form as an ATerm. Neither of these modes require store/DB write permission.
2004-10-25 * New language feature: with expressions.Eelco Dolstra5-13/+39
The expression `with E1; E2' evaluates to E2 with all bindings in the attribute set E1 substituted. E.g., with {x = 123;}; x evaluates to 123. That is, the attribute set E1 is in scope in E2. This is particularly useful when importing files containing lots definitions. E.g., instead of let { inherit (import ./foo.nix) a b c d e f; body = ... a ... f ...; } we can now say with import ./foo.nix; ... a ... f ... I.e., we don't have to say what variables should be brought into scope.
2004-10-25 * Allow certain operations to succeed even if we don't have writeEelco Dolstra9-16/+58
permission to the Nix store or database. E.g., `nix-env -qa' will work, but `nix-env -qas' won't (the latter needs DB access). The option `--readonly-mode' forces this mode; otherwise, it's only activated when the database cannot be opened.
2004-10-25 * Revert r1594 - it didn't solve the problem. Instead addEelco Dolstra1-1/+1
svn-revision to distributions, which should fix it.
2004-10-25 * Make sure that the prerelease version is included in `--version'.Eelco Dolstra1-1/+1
2004-10-14 * In `nix-env -q', sort derivations by name *without* caseEelco Dolstra1-1/+9
sensitivity.
2004-09-22 * Make store objects created by substitutes read-only.Eelco Dolstra1-0/+2
2004-09-12 * Fallback didn't work for subderivations of an unnormalised the mainEelco Dolstra1-44/+7
derivation, since NormalisationGoal would first run a NormalisationGoal on the subderivation (a no-op, since in a situation where we need fallback the successor is known), and then runs a RealisationGoal on the normal form, which then cannot do a fallback because it doesn't know the derivation expression for which it is a normal form. Tossed out the 2-phase normalisation/realisation in NormalisationGoal and SubstitutionGoal since it's no longer needed - a RealisationGoal will run a NormalisationGoal if necessary.
2004-09-10 * Operation `--delete-generations' to delete generations of aEelco Dolstra8-33/+100
profile. Arguments are either generation number, or `old' to delete all non-current generations. Typical use: $ nix-env --delete-generations old $ nix-collect-garbage * istringstream -> string2Int.
2004-09-09 * Remove write permission from store objects after they have beenEelco Dolstra1-0/+4
added to the store. Bug reported by Martin.
2004-09-09 * A very dirty hack to make setuid installations a bit nicer to use.Eelco Dolstra6-15/+74
Previously there was the problem that all files read by nix-env etc. should be reachable and readable by the Nix user. So for instance building a Nix expression in your home directory meant that the home directory should have at least g+x or o+x permission so that the Nix user could reach the Nix expression. Now we just switch back to the original user just prior to reading sources and the like. The places where this happens are somewhat arbitrary, however. Any scope that has a live SwitchToOriginalUser object in it is executed as the original user. * Back out r1385. setreuid() sets the saved uid to the new real/effective uid, which prevents us from switching back to the original uid. setresuid() doesn't have this problem (although the manpage has a bug: specifying -1 for the saved uid doesn't leave it unchanged; an explicit value must be specified).
2004-09-09 * Use setre[ug]id() instead of setres[ug]id(), since the former isEelco Dolstra2-5/+5
more common than the latter (which exists only on Linux and FreeBSD). We don't really care about dropping the saved IDs since there apparently is no way to quiry them in any case, so it can't influence the build (unlike the effective IDs which are checked by Perl for instance).
2004-09-09 * Set the umask to known value (0022). This is important in aEelco Dolstra1-0/+6
setuid installation, since the calling user may have a more fascist umask (say, 0077), which would cause the store objects built by Nix to be unreadable to anyone other than the Nix user.
2004-08-31 * Main the `substitutes-rev' table again, but now in a way thatEelco Dolstra3-21/+40
doesn't take \Theta(n^2) space/time complexity.
2004-08-31 * Quadruple the Berkeley DB locking limits to get rid of out of memoryEelco Dolstra1-2/+21
errors while running `nix-store --verify'.
2004-08-30 * Removed nrWaitees field. It was redundant with waitees.size() andEelco Dolstra1-24/+5
could get out of sync if multiple input derivations mapped to the same closure expression (since waitees is a set).
2004-08-25 * `--min-age' flag in nix-store and nix-collect-garbage to only deleteEelco Dolstra3-13/+35
unreachable paths that haven't been used for N hours. For instance, `nix-collect-garbage --min-age 168' only deletes paths that haven't been accessed in the last week. This is useful for instance in the build farm where many derivations can be shared between consecutive builds, and we wouldn't want a garbage collect to throw them all away. We could of course register them as roots, but then we'd to unregister them at some point, which would be a pain to manage. The `--min-age' flag gives us a sort of MRU caching scheme. BUG: this really shouldn't be in gc.cc since that violates mechanism/policy separation.
2004-08-25 * `nix-collect-garbage' now actually performs a garbage collection, itEelco Dolstra1-1/+1
doesn't just print the set of paths that should be deleted. So there is no more need to pipe the result into `nix-store --delete' (which doesn't even exist anymore).
2004-08-25 * Put the garbage collector in nix-store: operation `--gc',Eelco Dolstra6-19/+167
suboperations `--print-live', `--print-dead', and `--delete'. The roots are not determined by nix-store; they are read from standard input. This is to make it easy to customise what the roots are. The collector now no longer fails when store expressions are missing (which legally happens when using substitutes). It never tries to fetch paths through substitutes. TODO: acquire a global lock on the store while garbage collecting. * Removed `nix-store --delete'.
2004-08-24 * Validate derivation names. In particular don't allow spaces.Eelco Dolstra1-8/+19
* Drop support for the outPath attribute in derivations.
2004-08-20 * The gid should also match.Eelco Dolstra1-1/+1
2004-08-20 * Unbreak programs that are not setuid (such as nix-hash).Eelco Dolstra1-0/+3
2004-08-20 * On systems that have the setresuid() and setresgid() system calls toEelco Dolstra2-8/+26
set the real uid and gid to the effective uid and gid, the Nix binaries can be installed as owned by the Nix user and group instead of root, so no root involvement of any kind is necessary. Linux and FreeBSD have these functions.
2004-08-20 * Setuid support for sharing a Nix installation between multipleEelco Dolstra2-0/+88
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-08-18 * The default verbosity level of all Nix commands is now lvlInfo.Eelco Dolstra4-6/+5
* Builder output is written to standard error by default. * The option `-B' is gone. * The option `-Q' suppresses builder output. The result of this is that most Nix invocations shouldn't need any flags w.r.t. logging.
2004-08-11 * The predecessor of a successor need not be present. This inEelco Dolstra1-4/+6
particular happens on distributed builds or when using push/pull.
2004-08-05 * Clean up the temporary directory for hook communication (and don'tEelco Dolstra1-0/+1
print out incorrect "build failed" messages).
2004-08-04 * Every real language has a `map' function.Eelco Dolstra2-2/+19
2004-08-04 * Allow primops with more that 1 arguments.Eelco Dolstra7-104/+102
2004-08-04 * Creating a file nix-support/no-scan in the output path of aEelco Dolstra2-3/+6
derivation disables scanning for dependencies. Use at your own risk. This is a quick hack to speed up UML image generation (image are very big, say 1 GB). It would be better if the scanner were faster, and didn't read the whole file into memory.
2004-07-06 * Fixed format string error.Eelco Dolstra1-1/+1
2004-07-01 * Don't go into a (sometimes infinite) loop calling the build hook.Eelco Dolstra1-16/+24
2004-07-01 * Nix-instantiate now accepts sets of derivations (just like nix-env).Eelco Dolstra1-0/+9
2004-07-01 * Nix-env operations now by default filter out any derivations forEelco Dolstra1-9/+28
system types other than the current system. I.e., `nix-env -i' won't install derivations for other system types, and `nix-env -q' won't show them. The flag `--system-filter SYSTEM' can be used to override the system type used for filtering (but not for building!). The value `*' can be used not to filter anything.
2004-07-01 * Align the columns in the output of `nix-env -q'.Eelco Dolstra1-4/+36
2004-07-01 * Allow the system attribute of derivations to be queried inEelco Dolstra1-37/+50
`nix-env -q'. * Queries can now be combined, e.g., `nix-env -q --status --system'.
2004-07-01 * Include some missing headers.Eelco Dolstra2-0/+2
2004-06-29 * Write build logs to disk again.Eelco Dolstra1-1/+29
2004-06-28 * By default, `nix-env -i' now deletes previously installedEelco Dolstra1-3/+21
derivations with names matching the derivations being installed. The option `--preserve-installed / -P' overrides this behaviour.
2004-06-28 * In a realisation goal, check the result of the correspondingEelco Dolstra1-0/+6
normalisation goal.
2004-06-28 * `nix-env -u' now allows a specific version to be specified whenEelco Dolstra1-4/+7
upgrading. This fixes a bug reported by Martin: $ nix-env -i foo-1.0 $ nix-env -u foo-1.0 upgrading foo-1.0 to foo-1.1
2004-06-28 * Added a switch `--fallback'. From the manual:Eelco Dolstra11-54/+154
Whenever Nix attempts to realise a derivation for which a closure is already known, but this closure cannot be realised, fall back on normalising the derivation. The most common scenario in which this is useful is when we have registered substitutes in order to perform binary distribution from, say, a network repository. If the repository is down, the realisation of the derivation will fail. When this option is specified, Nix will build the derivation instead. Thus, binary installation falls back on a source installation. This option is not the default since it is generally not desirable for a transient failure in obtaining the substitutes to lead to a full build from source (with the related consumption of resources).
2004-06-25 * A flag `--keep-going / -k' to keep building goals if one fails, asEelco Dolstra5-139/+167
much as possible. (This is similar to GNU Make's `-k' flag.) * Refactoring to implement this: previously we just bombed out when a build failed, but now we have to clean up. In particular this means that goals must be freed quickly --- they shouldn't hang around until the worker exits. So the worker now maintains weak pointers in order not to prevent garbage collection. * Documented the `-k' and `-j' flags.
2004-06-25 * Don't throw an exception when a build fails. Just terminate theEelco Dolstra1-58/+214
goal and allow the problem to be handled elsewhere (e.g., at top-level).
2004-06-24 * Obsolete.Eelco Dolstra1-162/+0
2004-06-24 * Multiple and/or failing substitutes now work.Eelco Dolstra1-12/+42
generated by cgit-pink 1.4.1 (git 2.44.2) at 2024-12-23T03·58+0000