Open perplexedpigmy opened 1 month ago
Does this also store the selection criteria in config.json
, so that bin update --all
would work without manually selecting the package? If it does, that would be a huge improvement!
I'm currently running a system with an old version of GLIBC which occasionally prevents me from using the gnu
binaries (which I prefer over musl
if they work). When I first install a package the first time, I first pick gnu
, then go with musl
if it doesn't work. Later when I run bin update --all
, I've already forgotten which variant was the one that works and have to do this again.
@ristomatti Yes, the config.json
is storing all required information for bin update --all
to work automatically. btw, tagging me would make sure that a notification is sent to my email so I am aware of your query.
I found this
bin
utility useful and wanted to use it insideDockefile
s, which meant that at no point can we drop to a TTY, the simplest way to circumvent user feedback is to allow explicit selection. This PR suggests a minimal addition required to allow for explicit command line selection as well as a use case in the.devcontainer
added to the project. It is already being used, the PR is just in case the project maintainer find the added behavior desirable.Note: The README was not updated, as it currently doesn't explain in detail all the options and switches, this oversight can be remedied on request.
There are 2 minor updates:
Previously, the installation/download directory is derived from the
PATH
, when it's unable to do so, thebin
utility demands user feedback. In some cases it's useful to be able to shortcut this process and directly provide it with the installation directory using theBIN_EXE_DIR
Note: while the original
bin
utility allows for installation at a specific directoryThe behavior differs. Without
BIN_EXE_DIR
when the initial config is missing, the user will be requested to provide the installation directory.In some cases the release may contain multiple files and user intervention is required to choose which one to install. The select option was introduced to allow the user to specify the exact file to install even when it's inside an archive (tar, xz, etc).
While it is possible to select partially, IMHO it defeats my original purpose of avoiding any TTY interaction, but why not?!