3 ms·
> The version number should never appear in the command name. Well, that's nice in theory, but... > In 50+ years of typing into terminals, we have not figured
by scbrg 6y ago
> The version number should never appear in the command name.
Well, that's nice in theory, but...
> In 50+ years of typing into terminals, we have not figured out how to have multiple versions of things coexist peacefully.
Well, yes, we have. By making the version number appear in the command name. It's not a great solution, but it's a solution. And since you didn't really provide a better one, it's pretty silly to advice against using it.
Also, symlinks are a thing. Nobody (normally) invokes python3.7m directly. There's a symlink pointing to it (or more likely not, as it's probably not the python you want).
- jspaetzel 6y agoVersions should appear when you have multiple versions, not a default behavior.
- scbrg 6y agoI'm not sure how you envision that would work. Should the contents of a package mutate when another version of the same package is installed? Would you consider that to be a sane behavior?
- yjftsjthsd-h 6y agoNo, you use your package manager's alternatives system to manage who gets the "default" name.
- scbrg 6y agoYes, that's covered by the last paragraph of my initial comment - it's generally handled by symlinks already. jspaetzel seems to think this isn't good enough though, and that the commands should magically just have the non versioned name until multiple versions show up on the same system. I'm curious about how they envision that to work.