netbsd-sandbox
cargo-patch
netbsd-sandbox | cargo-patch | |
---|---|---|
2 | 1 | |
9 | 60 | |
- | - | |
10.0 | 2.8 | |
almost 4 years ago | 13 days ago | |
C | Rust | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
netbsd-sandbox
-
Testing the Lua kernel interpreter in NetBSD (2021)
There is also `secmodel_sandbox`, a proof of concept for a Lua-based application sandbox on NetBSD:
https://github.com/smherwig/netbsd-sandbox
I really wish it was picked up more. NetBSD has a lot of innovative ideas and it is sad to see it go so forgotten and neglected.
- Rust for the Kernel Could Possibly Be Merged for Linux 5.20
cargo-patch
-
Rust for the Kernel Could Possibly Be Merged for Linux 5.20
First commit 2 months ago, started with edition 2021. https://hg.sr.ht/~cyplo/legdur/browse/Cargo.toml?rev=ca11815...
Have you tried compiling something less than bleeding edge, with a year old compiler, or are you picking projects specifically to "showcase" the supposed failings of the Rust compiler?
Many libraries in the ecosystem have a MSRV (minimum support rust version) guarantee, with compile-time shims to enable newer features if a more recent version is detected.
You can pin your dependencies to those versions (and if they don't have an explicit MSRV, just pin it to a version by date or by running https://github.com/foresterre/cargo-msrv on the project to find the effective MSRV).
You can cargo install specific versions of a binary crate, and if they move to the 2021 edition, or use a recently stabilized standard library function or w/e, you can simply choose to install a specific version, that would work with your distro's rustc/cargo.
I'm not even talking about the completely valid, but last resort strategy of many non-bleeding edge distro package maintainers, of simply creating a .patch file and applying it. In legdur's case, --- edition = "2021" +++ edition = "2018" on Cargo.toml would probably do the trick. For libraries/binaries you control, you can use https://doc.rust-lang.org/cargo/reference/overriding-depende... and https://github.com/itmettkeDE/cargo-patch.
Giving up after the first minor roadblock and crying bloody murder is intellectually lazy.
What are some alternatives?
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
gccrs - GCC Front-End for Rust
cargo-deb - A cargo subcommand that generates Debian packages from information in Cargo.toml
surveys - Repo for coordinating the creation, distribution, collection, and analysis of surveys for the Rust project.
rust - Empowering everyone to build reliable and efficient software.
jakt - The Jakt Programming Language
rfcs - RFCs for changes to Rust
cargo-msrv - 🦀 Find the minimum supported Rust version (MSRV) for your project