Alejandro R Mosteo

Fair warning: even if you manage to compile `alr`, due to #849 you will likely have some odd behaviors (you'll have to rely on an external compiler, that's for sure)....

Thanks for the detailed report and research! We took some measures to make some warnings that can happen during `alr printenv` go to stderr, but these ones escaped. It's probably...

Thanks for the report, Stephane. Probably in this case we should check that the release doesn't exist taking into account only the community index. This is not a trivial change...

@Fabien-Chouteau I guess there's nothing blocking this one?

Perhaps we can add a config option to disable it?

Thanks, Maxim. I guess the list is computed correctly but in the first instance it is wrongly printed.

Thanks Simon, from the summary you provide in your last post it's clear what the problem is. We're fixing the file extension for the default executable name but not when...

For the CI site, we have a way to provide alternate testing via a `test` action. It would be a matter of providing a testing nested crate and invoke it...

Thanks for the report, will investigate. Meanwhile, selecting `None` twice should work if your plan is to use the external compiler.

Then `alr toolchain --disable-assistant`