nixpkgs/pkgs/tools/virtualization/nixos-container/default.nix

{ substituteAll, perl, shadow, util-linux }:

substituteAll {
    name = "nixos-container";
    dir = "bin";
    isExecutable = true;
    src = ./nixos-container.pl;
    perl = perl.withPackages (p: [ p.FileSlurp ]);
    su = "${shadow.su}/bin/su";
    utillinux = util-linux;

    postInstall = ''
      t=$out/share/bash-completion/completions
      mkdir -p $t
      cp ${./nixos-container-completion.sh} $t/nixos-container
    '';
}
treewide: use perl.withPackages when possible Since 03eaa48 added perl.withPackages, there is a canonical way to create a perl interpreter from a list of libraries, for use in script shebangs or generic build inputs. This method is declarative (what we are doing is clear), produces short shebangs[1] and needs not to wrap existing scripts. Unfortunately there are a few exceptions that I've found: 1. Scripts that are calling perl with the -T switch. This makes perl ignore PERL5LIB, which is what perl.withPackages is using to inform the interpreter of the library paths. 2. Perl packages that depends on libraries in their own path. This is not possible because perl.withPackages works at build time. The workaround is to add `-I $out/${perl.libPrefix}` to the shebang. In all other cases I propose to switch to perl.withPackages. [1]: https://lwn.net/Articles/779997/ 2021-02-24 20:53:45 +01:00			`{ substituteAll, perl, shadow, util-linux }:`
nixos-containers: init package (#16959) This moves nixos-containers into its own package so that it can be relied upon by other packages/systems. This should make development using dynamic containers much easier. 2016-07-19 08:13:06 +02:00
			`substituteAll {`
			`name = "nixos-container";`
			`dir = "bin";`
			`isExecutable = true;`
			`src = ./nixos-container.pl;`
treewide: use perl.withPackages when possible Since 03eaa48 added perl.withPackages, there is a canonical way to create a perl interpreter from a list of libraries, for use in script shebangs or generic build inputs. This method is declarative (what we are doing is clear), produces short shebangs[1] and needs not to wrap existing scripts. Unfortunately there are a few exceptions that I've found: 1. Scripts that are calling perl with the -T switch. This makes perl ignore PERL5LIB, which is what perl.withPackages is using to inform the interpreter of the library paths. 2. Perl packages that depends on libraries in their own path. This is not possible because perl.withPackages works at build time. The workaround is to add `-I $out/${perl.libPrefix}` to the shebang. In all other cases I propose to switch to perl.withPackages. [1]: https://lwn.net/Articles/779997/ 2021-02-24 20:53:45 +01:00			`perl = perl.withPackages (p: [ p.FileSlurp ]);`
Revert "nixos-container: Use machinectl shell (#18825)" This reverts commit c37e76b4d2ac59139df8956cc2b1ec6921bea11d. Unfortunately, using "machinectl shell" has two bad side effects: * It sends the command's stderr to stdout. * It doesn't propagate the command's exit status. This broke NixOps. PR #18825. 2017-03-21 16:45:47 +01:00			`su = "${shadow.su}/bin/su";`
utillinux: rename to util-linux 2020-11-24 16:29:28 +01:00			`utillinux = util-linux;`
nixos-containers: init package (#16959) This moves nixos-containers into its own package so that it can be relied upon by other packages/systems. This should make development using dynamic containers much easier. 2016-07-19 08:13:06 +02:00
			`postInstall = ''`
tree-wide: unify Bash completions outputs (#103421) Use $out/share/bash-completion/completions to store the Bash completions 2020-11-12 22:22:18 +01:00			`t=$out/share/bash-completion/completions`
nixos-containers: init package (#16959) This moves nixos-containers into its own package so that it can be relied upon by other packages/systems. This should make development using dynamic containers much easier. 2016-07-19 08:13:06 +02:00			`mkdir -p $t`
			`cp ${./nixos-container-completion.sh} $t/nixos-container`
			`'';`
			`}`