prick-exec 2026.819.2

Child process launch, signal handling and environment guards for `prk run`.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48

[package]
name = "prick-exec"
description = "Child process launch, signal handling and environment guards for `prk run`."
version.workspace = true
edition.workspace = true
rust-version.workspace = true
license.workspace = true
repository.workspace = true
homepage.workspace = true
authors.workspace = true

[dependencies]
prick-core = { workspace = true }
secrecy = { workspace = true }
thiserror = { workspace = true }

# The SIGPIPE reset and the signal mask, both of which happen between fork and
# exec and so must be async-signal-safe.
[target.'cfg(unix)'.dependencies]
libc = { workspace = true }

# `which` is PATHEXT-aware, which is the whole reason it is here: `npm` on
# Windows is `npm.cmd`, and std's own resolution only ever appends `.exe`.
[target.'cfg(windows)'.dependencies]
which = { workspace = true }
windows-sys = { workspace = true, features = [
  "Win32_Foundation",
  "Win32_Security",
  "Win32_Security_Authorization",
  "Win32_System_Console",
  "Win32_System_JobObjects",
  "Win32_System_Memory",
  "Win32_System_Threading",
] }

[dev-dependencies]
tempfile = { workspace = true }

# A test fixture, not a shipped artefact. The integration tests need a process
# that calls into this crate and is then *replaced* by `exec`, which the test
# harness itself cannot be. It is a real bin target so that cargo sets
# CARGO_BIN_EXE_prick-exec-child for the tests and there is no path guessing.
[[bin]]
name = "prick-exec-child"
path = "src/bin/child.rs"

[lints]
workspace = true