Global configuration file

[awvwgk]

It might be a good point to think about having a global configuration file for fpm in ~/.fpmconfig or ~/.config/fpm/config.toml. This would allow to set global options which do not affect how packages are built, but how fpm interacts with the user or environment.

For example it would allow to disable using environment variables in fpm for compiler detection if this is an unwanted feature for some user or to enable colored output.

[epagone]

This would allow to set global options which do not affect how packages are built, but how fpm interacts with the user or environment.

So if I would like to set by default a certain profile (say debug, to be overridden to release when necessary) or a certain compiler, this is not going to be the right place, correct?

[awvwgk]

So if I would like to set by default a certain profile (say debug, to be overridden to release when necessary) or a certain compiler, this is not going to be the right place, correct?

As a user specific file, settings there should not be crucial for successfully building a project. I think a default profile or compiler could be borderline, but I wouldn't rule those out completely. In any case we have to design it very carefully.

[awvwgk]

Will submit a patch for this as follow-up for #549

[urbanjost]

.The metadata created by "fpm new" would be nice. I was playing with a TOML file for that and got sidetracked I would like to have defaults for at least

license = "license"
author = "Jane Doe"
maintainer = "jane.doe@example.com"
copyright = "Copyright 2021, Jane Doe""
homepage="xxxxxxxxxxxxxxxx"

if that has not already been considered, and the default install directory; and I think the compiler would be nice as long as FPM_COMPILER overrides it or use of environment variables is not turned off.

[urbanjost]

Curious if you are thinking of serial data like fpm.toml file or something that would allow conditionals and aliases or something like the response files too?

[awvwgk]

Minh @minhqdao, this could be relevant to have for the fpm registry project to store for example the path to the local registry.

Will submit a patch for this as follow-up for #549

Looks like I never came to that point last year 😅