Alejandro R Mosteo
Alejandro R Mosteo
Although it's now possible to relocate both config+cache as a whole with `-c`/`ALR_CONFIG`, it could be useful to relocate just the cache even when using the default configuration.
Running `alr config --set msys2.do_not_install true` will still cause the installation to begin.
This could be standard behavior, but I'm reporting just in case. I have the widget configured with weighted sorting and default bias. This works well for a few days in...
So, initialization, commiting, pushing, pulling, all work OK. Problem arises when I try to clone an existing remote in another location. The steps to reproduce are: ``` - cd /tmp...
Created via `alr publish` with `alr 2.1.0-dev`
To avoid making clients of a SPARK library depend on `gnatprove` itself, we should move that dependency to a nested prover crate.
If a looping softlink exists somewhere in the crate, commands using `Alire.Directories.Find_Files_Under` will break (e.g., `alr run`).
Manual changes in our manifest trigger an update, but changes in linked crates do not. This sometimes may cause problems with inconsistent solutions, which go away with the needed `alr...
For now it just prints a very simple summary: ``` $ alr cache Path: /home/jano/.local/share/alire Size: 5.0 GiB ``` But the building blocks are there in `Alire.Cache` for more sophisticated...