Closed infinity0 closed 8 months ago
matthiaskrgr
commented
5 years ago What's the plan on preventing false positives for projects that are never meant to get inside debian (private or commercial applications)? Is it possible to check the license maybe?
ignatenkobrain
commented
5 years ago I don't think that cargo has anything to do with this..
infinity0
commented
5 years ago What's the plan on preventing false positives for projects that are never meant to get inside debian (private or commercial applications)?
Don't upload them to crates.io?
I don't think that cargo has anything to do with this..
Why not?
infinity0
commented
5 years ago For now, we were forced to rename fd to /usr/bin/fdfind in Debian.
An alternative solution is being discussed where we install all cargo binaries to /usr/lib/cargo/bin and then symlink them into /usr/bin unless there is a conflict like the fd case. Then if people want to call fd in cross-platform shell scripts they can just export PATH=/usr/lib/cargo/bin:$PATH at the top of their shell scripts rather than some complex if-statement involving fd/fdfind.
Please take this issue seriously rather than downvoting me without explanation.
alerque
commented
3 years ago An alternative solution is being discussed where we install all cargo binaries
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.
epage
commented
8 months ago 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
fdandbatare 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:
For a full list of binaries see https://gist.github.com/infinity0/1ae795f75d35b5db39a6413584ea9f3d