- 
                Notifications
    You must be signed in to change notification settings 
- Fork 52
Allow a 'paths-relative-to' key in the firmware config #70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR! I've requested a few changes. There's also a linter error, so you might want to run "ruff check" on your sources.
a3804c3    to
    0d20174      
    Compare
  
    There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, thanks for handling the requested changes. Seems like two small mistakes got in the first commit, once these are dealt with I'll merge this PR.
… final fw_configs fw_configs will always be a dictionnary, but individual ones might not.
f567175    to
    9550c64      
    Compare
  
    configs paths-relative-to can be CWD, THIS_FILE, or a literal path. It defaults to CWD. The firmware configs will be patched accordingly: binary paths will be prefixed by either the current working directory (this is the old behaviour), the directory containing the firmware config file, or the literal path. Signed-off-by: Félix Piédallu <[email protected]>
9550c64    to
    f4a674e      
    Compare
  
    This new option of the configuration file indicates that paths to images are relative to a specific path. Signed-off-by: Félix Piédallu <[email protected]>
f4a674e    to
    03865c2      
    Compare
  
    | Thanks! | 
Closes #68
paths-relative-to can be CWD, THIS_FILE, or a literal path. It defaults
to CWD.
The firmware configs will be patched accordingly: binary paths will be
prefixed by either the current working directory (this is the old
behaviour), the directory containing the firmware config file, or the
literal path.
Let me know if you prefer the CWD behaviour to do nothing (like the current behaviour) instead of prefixing with os.getcwd().