| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
flake-compat 009399224d (2022-11-17) -> 0f9255e01c (2023-10-04)
nixpkgs bb31220cca (2022-12-19) -> e97b3e4186 (2023-12-11)
utils 5aed5285a9 (2022-11-02) -> 4022d587cb (2023-12-04)
|
|
|
|
|
|
|
|
| |
flake-compat 64a525ee38 (2022-03-25) -> 009399224d (2022-11-17)
nixpkgs 30d3d79b7d (2022-03-25) -> bb31220cca (2022-12-19)
utils 0f8662f131 (2022-03-26) -> 5aed5285a9 (2022-11-02)
Co-authored-by: Flake Update Bot <operations+update@serokell.io>
Co-authored-by: Alexander Bantyev <balsoft@balsoft.ru>
|
|
|
|
|
|
| |
flake-compat b7547d3eed (2022-01-03) -> 64a525ee38 (2022-03-25)
nixpkgs 7f65e4abd5 (2022-01-29) -> 30d3d79b7d (2022-03-25)
utils 846b2ae0fc (2022-01-20) -> 0f8662f131 (2022-03-26)
|
|
|
|
|
|
| |
flake-compat 12c64ca55c (2021-08-02) -> b7547d3eed (2022-01-03)
nixpkgs e0ce3c683a (2021-09-19) -> 7f65e4abd5 (2022-01-29)
utils 7e5bf3925f (2021-09-13) -> 846b2ae0fc (2022-01-20)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Flake lock file changes:
• Updated input 'flake-compat':
'github:edolstra/flake-compat/99f1c2157fba4bfe6211a321fd0ee43199025dbf' (2020-11-26)
→ 'github:edolstra/flake-compat/12c64ca55c1014cdc1b16ed5a804aa8576601ff2' (2021-08-02)
• Updated input 'nixpkgs':
'github:NixOS/nixpkgs/d8eb97e3801bde96491535f40483d550b57605b9' (2021-06-06)
→ 'github:NixOS/nixpkgs/e0ce3c683ae677cf5aab597d645520cddd13392b' (2021-09-19)
• Updated input 'utils':
'github:numtide/flake-utils/7d706970d94bc5559077eb1a6600afddcd25a7c8' (2021-05-31)
→ 'github:numtide/flake-utils/7e5bf3925f6fbdfaf50a2a7ca0be2879c4261d19' (2021-09-13)
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add xcbuild as native build input 2 ways & pass --verbose to cargo build
* Make "deploy" build on macOS
* Bump the nixpkgs version to one that ships Rust 1.47, which can
produce binaries under macOS 11 (Big Sur).
* Use darwin-specific options that let Naersk build the "deploy"
binary under macOS. (With a work-around for
https://github.com/nmattia/naersk/issues/127, which prevents this
from being much more straight-forward).
Unfortunately, the "activate" binary can't be built under macOS due to
the inotify dependency; that means the best we can do is to run the
deploy under macOS, not deploy *to* macOS.
|
| |
|
| |
|
|
|