riir runCommand2 and remove environ
crimes #284
Labels
No labels
Area/build-packaging
Area/cli
Area/evaluator
Area/fetching
Area/flakes
Area/language
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/store
bug
crash 💥
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
imported
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
RFD
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
ux
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#284
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
we have extremely suspect uses of
extern char **environ
, with weak symbols, evil repetition and more. these may cause some build breakage on freebsd if-Wl,-z,defs
is present. also runCommand2 is just generally not very good API. Fixing that API is probably a reasonable second step, but can be done as a first step if in fact required.rust tends to have reasonable implementations of wrapping the truly horrible Unix APIs, and we can use
CommandExt
for pretty much everything it does.Action items:
getEnvs
runCommand2
in terms of this new more-declarative primitive.Commit suggestions: