-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Encourage or enforce descriptive binary names with low chance of conflict #6001
Comments
What's the plan on preventing false positives for projects that are never meant to get inside debian (private or commercial applications)? |
I don't think that cargo has anything to do with this.. |
Don't upload them to crates.io?
Why not? |
For now, we were forced to rename An alternative solution is being discussed where we install all cargo binaries to Please take this issue seriously rather than downvoting me without explanation. |
Binaries are just binaries, there isn't something intrinsic that makes them "cargo binaries" other than they happen to use the same build tooling. This sounds like an ecosystem culture problem more than a tooling problem. I don't think the tooling restricting what you can or can't name a binary is necessarily productive, but some documentation nudges might be fair game. People grabbing their favorite short name without bothering to look around the bredth of *nix ecosystems, then later their project gaining popularity is the issue here. Some nudges in the docs to check something like Repology before picking a bin name if they intend their package to be distributed is probably a good thing. |
As I'm not really seeing anything actionable that cargo can (how do we decide what is low chance of conflict?) or should (applications exist in a variety of contexts) do, I'm going to close this. If there is a reason we should re-evaluate this, let us know! |
Some crates like
fd
andbat
are causing us extra work in trying to get them into Debian.It would be good if cargo encouraged people not to choose binary names that are likely to conflict with others.
For reference, as of 2018-09-09 the list of existing 1-4-character binaries in Debian Unstable is:
The text was updated successfully, but these errors were encountered: