diff options
| author | Asherah Connor <ashe@kivikakk.ee> | 2025-07-31 17:15:19 +1000 |
|---|---|---|
| committer | Asherah Connor <ashe@kivikakk.ee> | 2025-08-02 12:52:16 +1000 |
| commit | 6c8c88c6229534778cfa03a8a1fd83aa198a79de (patch) | |
| tree | 4dc7957d2a20afede698508e39fb7e6caba7315c /pkgs/development/python-modules/python-openstackclient/git@git.tavy.me:nixos | |
| parent | ed33ba16ce8e8605d8e9ef2dc6e802bc3134781d (diff) | |
buildMix: default to removing target config
See previous discussion at https://github.com/NixOS/nixpkgs/pull/429770.
cc @adamcstephens.
This is equivalent to giving `appConfigPath` an empty directory, but
expresses intent better (and doesn't require throwing an empty directory
into the store).
The Elixir ecosystem assumes [1] that dependencies are compiled without
their config; the `config/` directory is therefore used in library-only
projects to supply config values only intended for use when _developing_
them. This leads to errors only seen in Nix when compile-time config
lacks runtime equivalents in end-user applications (per the whole
conversation at [1]).
Right now, the only way to get `buildMix` to build without config is to
manually remove the target's config directory in a hook/override, or (as
above) give `appConfigPath` an empty directory. This PR adds a clearer
mechanism, and makes it the default.
[1] https://github.com/dashbitco/lazy_html/pull/11#issuecomment-3138715485
Tested with a `mix2nix`-using package that this functions as expected,
and with some `deps_nix`-using ones that `appConfigPath` still does too.
Diffstat (limited to 'pkgs/development/python-modules/python-openstackclient/git@git.tavy.me:nixos')
0 files changed, 0 insertions, 0 deletions
