Hello,

I have only one configuration file for buildstream, on
~/.conf/buildstream.conf, and I configured as:

$ cat ~/.config/buildstream.conf | grep artifa
artifactdir: /data/Projects/Buildstream/build/artifactdir

but for some reason my buildstream assumed that it should store my
artifacts on ~/.cache/ filling up completely my disk and I had to create a
bootable usb stick using my wife's computer, as I could not even login
anymore (no space on /tmp, no space on /), /data my old 2tb HDD that I use
for compilation.

So I propose something simple, but that *might* solve this kind of issue, a
new addition to core (as I don't know how to provide this outside core, if
it's possible I'm all ears) that you can query all the maps and definitions
from the yaml configuration (or defaults, if none).

Example usage of the things I imagine:

$ bst query-config --config-file
/home/username/.conf/buildstream1.bst
/home/username/.conf/buildstream.bst

$ bst query-config --list-possible-keys
sourcedir: string      folder to store the sources
artifactdir: string      folder to store the cached artifacts
...
logdir: string            folder to store the logs

$ bst query-config --show-config
(result of print(yaml_map here))

$ bst query-config --key cachedir
cache-dir is only availble on buildstream 2.0, please check if you are
using the correct version

$ bst query-config --key "projects.gnome"
gnome: {
    strict: false
}

$ bst query-config --key "logdir"
/data/something/log

This way I could have queried the current file and folder used for
artifacts withotu assuming that the configuration file was correct - I
still don't know that it is.

Tougths?
Tomaz

Reply via email to