When installing larger packages (e.g. google-chrome) which take a while, it’d be useful to get some more feedback on what is happening. The --verbose or -v options don’t seem to change the output level currently (I’ve tried both “flox install -v google-chrome” and “flox -v install google-chrome”).
Hej @t0rx
Thank you for reporting on your difficulties.
We are aware of this limitation in our logging.
In fact currently we simply collect output emitted by our builds, without forwarding it, while we show a spinner indicating progress, clearly during long downloads or builds of uncached software, this is not satisfactory.
Since the builds of environments are performed “out of process” we are still discussing the correct war of integrating the output in the in-process logging and verbosity setup (which is controlled by the verbosity flag)