* mixRelease: format code by nixpkgs-format
* mixRelease: investigate why erlang is referenced in resulting derivation
* mixRelease: organize nativeBuildInputs and buildInputs
It:
+ organizes `nativeBuildInputs` in a structured way.
+ moves `builtins.attrValues mixNixDeps` to `nativeBuildInputs`, because it's only used in compile-time
* mixRelease: remove current attempt for removing erlang references in resulting derivation
As said in the comment about "remove erlang references in resulting
derivation", for now, we don't have a robust method to do that.
Although these removed code did some work, they did not achieve the
final goal - remove erlang references in resulting derivation.
Therefore, it is better to remove them and provide future implementation
with a clean foundation.
> If you want to find these old codes, you can also retrieve them from
> the git history.
* mixRelease: remove all files for Microsoft Windows
* mixRelease: add new option - `removeCookie`
* mixRelease: polish comments
+ Capitalize the sentences.
+ Add punctuation marks.
+ Format a little code.
* mixRelease: wrap programs in $out/bin with their runtime deps
* mixRelease: commit what happysalada suggests
---------
Co-authored-by: c4710n <c4710n@users.noreply.github.com>
* fix: only substitute ERTS for escript builds in rebar3Relx
Previously beamPackages.rebar3Relx substituted references to erlang
for all builds, which only works for escript builds.
Fixes#261354
* doc: add comment mentioning fixed issue
Avoid the following during mix releases:
```
warning: the VM is running with native name encoding of latin1 which may
cause Elixir to malfunction as it expects utf8. Please ensure your
locale is set to UTF-8 (which can be verified by running "locale" in
your shell)
```
Avoid the following during mix builds:
warning: the VM is running with native name encoding of latin1 which may
cause Elixir to malfunction as it expects utf8.
This flag appears to cause issues in 3 out 4 users of mixRelease in
Nixpkgs, plus Mobilizon, which isn't merged yet. It might be safer to
set it to fals for now, as the runtime error messages produced by it are
quite cryptic.
The erlang language server's primary binary is `erlang_ls`, just like
the repository name, but this package sets the package name to
`erlang-ls` without also either aliasing the binary or setting
`meta.mainProgram`. Setting `meta.mainProgram` to `erlang_ls` should
allow the use of `lib.getExe`.
Currently, when fetchMixDeps is executed without mixEnv argument.
"mixEnv" envvar is empty at installPhase, instead of having value "prod".
This happens because optional attrs values are not included in @attrs variable.
Thrus being necessary to replace mixEnv for MIX_ENV, which holds value "prod".
Reference: https://github.com/NixOS/nixpkgs/pull/216214#issuecomment-1434737238
