Rust 1.50.0 incorporated a Cargo change (rust-lang/cargo#8937) in
which cargo vendor erroneously changed permissions of vendored
crates. This was fixed in Rust
1.51.0 (rust-lang/cargo#9131). Unfortunately, this means that all
cargoSha256/cargoHashes produced during the Rust 1.50.0 cycle are
potentially broken.
This change updates cargoSha256/cargoHash tree-wide.
Fixes#121994.
Introduce [`t-rec`](https://github.com/sassman/t-rec-rs), a terminal
recorder.
Usage:
```bash
nix run .#t-rec
```
Upon exit, `t-rec` will save recordings of the session to disk in GIF
and MP4.
Signed-off-by: Ana Hobden <operator@hoverbear.org>
The transmission conflict was non-trivial:
- libbrotli added to apparmor rules <1bdda029cd>
- apparmor rules rewritten <b280e64078>
Chosen the rewrite and verified that brotli is part of the rule set generated by `apparmorRulesFromClosure`.
In order for the ms-python.python extension to work these days,
we also need the ms-toolsai.jupyter extension. To permit easy
upgrades and to honour the principle of least surprise, we
wrapper the Python extension to include the Jupyter one. The
reverse is not true, you *can* have the Jupyter extension without
the Python one, so the reverse is not also done.
Signed-off-by: Daniel Silverstone <dsilvers@digital-scurf.org>
This splits off part of the Python extension into Microsoft's jupyter
extension, so this is necessary but not sufficient.
Signed-off-by: Daniel Silverstone <dsilvers@digital-scurf.org>
Also begin to start work on cross compilation, though that will have to
be finished later.
The patches are based on the first version of
https://reviews.llvm.org/D99484. It's very annoying to do the
back-porting but the review has uncovered nothing super major so I'm
fine sticking with what I've got.
Beyond making the outputs work, I also strove to re-sync the packages,
as they have been drifting pointlessly apart for some time.
----
Other misc notes, highly incomplete
- lvm-config-native and llvm-config are put in `dev` because they are
tools just for build time.
- Clang no longer has an lld dep. That was introduced in
db29857eb3, but if clang needs help
finding lld when it is used we should just pass it flags / put in the
resource dir. Providing it at build time increases critical path
length for no good reason.
----
A note on `nativeCC`:
`stdenv` takes tools from the previous stage, so:
1. `pkgsBuildBuild`: `(?1, x, x)`
2. `pkgsBuildBuild.stdenv.cc`: `(?0, ?1, x)`
while:
1. `pkgsBuildBuild`: `(?1, x, x)`
2. `pkgsBuildBuild.targetPackages`: `(x, x, ?2)`
3. `pkgsBuildBuild.targetPackages.stdenv.cc`: `(?1, x, x)`
