Deprecate UAPI bindings, to be removed in 1.0

Open
#4,573 2 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
linux, rust

Research direction

Start by locating the Linux UAPI bindings in the libc crate and reviewing how they are exposed to users. Compare the intended replacement with the linux-raw-sys documentation; done means the bindings are deprecated or removed as planned and users are clearly directed to that crate.

Written by the indexing model from the issue text.

Description

E-help-wanted O-linux

We talked at RustWeek and decided that we should remove bindings to the Linux UAPI from this crate. UAPI is huge and changes frequently so is difficult to maintain, and it's not a "libc". Instead, we would like to guide users toward the linux-raw-sys crate, which covers much more because bindings are autogenerated (and the crate is also more organized).

@Amanieu does this sound accurate?

Cc linux-raw-sys maintainer @sunfishcode in case you have any concerns with the above.

Dominant language
Rust
Stars
2.6k
Forks
1.3k
Avg merge
2d 13h
Merged PRs (30d)
27

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rust-lang/libc

All issues in rust-lang/libc

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.