Renaming fpm could help to avoid some confusion

[rouson]

TL/DR: Given fpm's support for building C and C++ projects, a name change could help to avoid initial misconceptions. Something like "Fun Package Manager" or "Fantastic Package Manager" would preserve the acronym fpm, and either name would accurately describe my experience of fpm. 😄

Motivation

I've had several recent experiences with introducing fpm to a project wherein the developers were unfamiliar with fpm and understandably assumed fpm is limited to building Fortran. Given recent very positive experiences I've had with building C and C++ projects with fpm, it would be nice to at least prevent this one obvious and avoidable source of confusion. To wit, I contributed a three-line (not counting one blank line) manifest to the SuperLU linear algebra package, which GitHub reports is 95% C and only 0.3% Fortran. I also forked Armadillo, a C++ project, and added a one-line fpm manifest that suffices for building it as a dependency of another project.

[perazz]

That's an amazing result, thank you for posting that @rouson - I wonder what happens in case of more complicated header folder structures, but still, it's pretty remarkable!