Disclaimer: AI used in the creation of the software
There is also an accompanying site https://omnibin.dev/ for you to browse
Disclaimer: AI used in the creation of the software
There is also an accompanying site https://omnibin.dev/ for you to browse
Cool hack! But… why put it in a bin directory when these commands exist?
I’m all for fun hacks that don’t really accomplish anything, but it’s weird that this does not even mention mvs run/shell.
They are different?
mvs lets you pick individual packages across the multiverse but this just adds them all – I guess it’s mvs-maximallized
I don’t see the real use-case where the difference between between mvs run package@version and running package@version from PATH which is essentially an alias to that (if I’m reading this correctly) matters.
How does it handle executables with the same name?
A few rules here: Using it · omnibin
an attribute named after the executable beats one that is not
a newer last-seen date beats an older
a shorter attribute name beats a longer
lexicogrpahic sort afterwards
eg. python3 comes from the python3 attribute rather than from python3Full, and a bare name resolves to the same package for everybody.
Pretty sure it’s meant to be a more ergonomic form of comma, which just downloads the binaries you need to run the commands you want. It’s similar to prepending comma’s , to every command I guess. (EDIT: plus some version magic)
It’s an interesting idea to consider, even if I don’t consider it an interesting idea for my setups.