You need to sign in or sign up before continuing.
'true' by itself is parsed as 'True' in .bst files
Summary
In a .bst file, if I have a list item 'true', it will be parsed as 'True'. The same for 'false'. This appears to be an artefact of yaml interpreting it as an actual boolean value.
For example, this manual element will try to execute 'True' rather than 'true' during configure:
kind: manual
(@): includes/important_things
config:
configure-commands:
- true
This isn't a very important issue. I sometimes do use stuff like this to debug my bst files.
Steps to reproduce
Adapting the great BuildStream first project doc:
# Note that your filesystem needs to be case-sensitive for this to fail.
bst init --project-name first-project
mkdir elements
cat > elements/true.bst <<EOF
kind: import
# Use a local source to stage our file
sources:
- kind: local
path: true
EOF
touch true
bst build true.bst
What is the current bug behavior?
In the repro example, you will see:
true.bst [line 6 column 8]: Specified path 'True' does not exist
What is the expected correct behavior?
The element should build successfully.