about summary refs log tree commit diff
path: root/pkgs/profpatsch/execline/run-execline.nix
Commit message (Collapse)AuthorAgeFilesLines
* pkgs/profpatsch/runExecline: move to writeCommand formProfpatsch2019-09-261-6/+7
| | | | | | | | It’s conventional that these tools have the form tool name options data so we should adhere to that.
* pkgs/profpatsch/runExecline: move to listProfpatsch2019-09-261-3/+8
| | | | | We can auto-escape execlines correctly if we model them as nix-style lists, so we shoud certainly do so. It also helps abstraction.
* machines/haku: open less ports in firewallProfpatsch2019-05-161-0/+1
|
* pkgs.profpatsch: switch to different import schemeProfpatsch2018-09-221-6/+6
| | | | | Reference files in `bin` outputs for a derivation as an attribute set, with renaming capabilities.
* More execline experiments & testingProfpatsch2018-09-211-7/+33
| | | | | | Improves the “execline experience” and adds some basic tests. The idea is that the final result doesn’t use coreutils and provides a feasible alternative to bash-based tooling.
* pkgs/profpatsch: WIP execline experimentsProfpatsch2018-07-251-0/+38
* runExecline: like runCommand, but a lot more lightweight * symlink: symlink a given list of links together * importer: a small DSL to “import” “modules” into a build context Some highlights: * runExecline does not use any stdenv (apart from the `execline` build) * symlink uses netstrings to pass correct fields into the derivation * no use of bash, everything uses execline.