How to support packages that do not conform to our "standard layout" (to be specified...) about fpm HOT 1 OPEN

Yes, I think fpm.toml for each project should include the exact commands that need to be executed to build the package, very much like we do in yml files for CI.

That said, until a need arises, I'd suggest that we take this approach for all packages, including those built with CMake, autotools, or plain Makefiles.

If we can make a package build in CI, we should be able to build it by fpm by making it execute commands specified in fpm.toml.

The way to do that is that we create a new repository, say certik/lapack.fpm

Does this even need to be a separate repo? Are you thinking about a repo that would be the registry of all fpm-supported packages, like what I described in #4 ?

from fpm.