Laurence Kedward

> ... we arrived at the conclusion that this is currently not easily possible. To be clear, I am not aware of any fundamental reason why this cannot be done,...

I made an attempt at this a while back (see [this post](https://github.com/fortran-lang/fpm/pull/505#issuecomment-872927759)) but didn't get a chance to finish it off and the code was a little hectic. You can...

Reopening for some outstanding tasks: - [ ] Command to print last set of build messages (https://github.com/fortran-lang/fpm/pull/622/#issuecomment-982687082) - [ ] Only print verbose output for the current package (not dependencies)...

Thanks @wyphan and @zoziha - fpm was not originally envisaged to be a binary package manager (I think), because of fundamental incompatibilities between different compilers and different versions. As already...

Hi @chuckyvt, thanks for taking the time to look into this and report here. I'd not heard of that restriction before, it seems quite limiting. One way to get this...

This is a sensible approach. I think it would be beneficial to be able to specify a local path. For parsimony it makes sense to use TOML for the registry...

I had envisaged that *fpm* would only interact with the index file since it can convey information stored within the package manifest without needing to download the package. Generating the...

I agree this is should be a simple area to prototype such features, however I'm not a fan of the proposed manifest syntax. IMO, this seems to be more of...

It would be good to get this implemented so that we can self-bootstrap Fortran *fpm* with parallel builds enabled. I am however still opposed to the treatment of *OpenMP* as...

Can these cases not also be specified in the `[build]` table, _e.g._: ```toml [build] openmp = true openmp-version = "^4.5" openmp-library = "iomp5" ``` We will already need logic for...