chcon, runcon: Use compile_error! to prevent incorrectly distributing them
Open
Nobody has claimed this yet.
U - chcon
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
Distributors do not want to publish them if Makefile included a bug by some reason.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the chcon and runcon implementations and the Makefile paths involved in distributing them. Read how compile_error! could be applied, then verify that the resulting build behavior prevents these commands from being incorrectly published when the Makefile contains the reported bug.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100