Semi-automatic update. These checks were performed:
- built on NixOS
- found 56c in filename of file in /nix/store/88xmgl9p82fph7d8qqzp48iqvkh688jd-mksh-56c
cc "@AndersonTorres @joachifm"
As-is the use of 'configureFlags="..."' breaks cross compilation
as it drops the configure platforms arguments.
Set zprofile separately to handle $out.
`bash-completion` lazy loads completion scripts by looking up the command name
in the completion directory. As such we need to create a symlink for every
nix command.
The problem had been masked by nixos sourcing all completion scripts on startup.
To use, add this option to your configuration.nix:
`programs.zsh.promptInit = "source ${pkgs.zsh-powerlevel9k}/share/zsh-powerlevel9k/powerlevel9k.zsh-theme";`
As per #30645, fish with fish-foreign-env prints this
(harmless) warning:
```
set: Tried to change the read-only variable “_”
```
This patch was developed by @rnhmjoj in the aforementioned
issue discussion
I don't know where this comes from (I accidentally did that as well
once), but some derivations seem to use `buildPhases` rather than
`phases` in their derivations.
This kills all improper usages as the lack of a `phases` argument
didn't break the build, so this can be safely removed.
The biggest benefit is that we no longer have to update the registry
package. This means that just about any cargo package can be built by
nix. No longer does `cargo update` need to be feared because it will
update to packages newer then what is available in nixpkgs.
Instead of fetching the cargo registry this bundles all the source code
into a "vendor/" folder.
This also uses the new --frozen and --locked flags which is nice.
Currently cargo-vendor only provides binaries for Linux and
macOS 64-bit. This can be solved by building it for the other
architectures and uploading it somewhere (like the NixOS cache).
This also has the downside that it requires a change to everyone's deps
hash. And if the old one is used because it was cached it will fail to
build as it will attempt to use the old version. For this reason the
attribute has been renamed to `cargoSha256`.
Authors:
* Kevin Cox <kevincox@kevincox.ca>
* Jörg Thalheim <Mic92@users.noreply.github.com>
* zimbatm <zimbatm@zimbatm.com>
