Hi -
> [...] I could also see file-based config being useful if some
> aspect of the debuginfod configuration can change from
> moment-to-moment. Environment variables could be used for that, but
> it would require either changing those variables in the calling
> shell or wrapping each debuginfod client utility.
So-so ... if the file contents are modified, but the environment
variable that points to the file is fixed, then one may get into parse
race conditions as different debuginfod client objects in the process
may be active at the same time.
> [...] You could also do this more granularly:
> DEBUGINFOD_HEADERS_FILES would work for us, and other lists could be
> created for other dynamically controllable aspects of the system.
> [...]
I see some value in doing this sort of thing more broadly,
hypothetically, but it's vague/speculative enough that I'd be just as
glad to limit the concept to the present case ("also add all headers
in given file"). So how about a $DEBUGINFOD_HEADERS and perhaps
$DEBUGINFOD_HEADERS_FILE env vars for now?
- FChE
