Skip to content

fix: preserve resources fields in tw.yaml#295

Open
kranurag7 wants to merge 1 commit intomainfrom
kr/3414fea634256ae8
Open

fix: preserve resources fields in tw.yaml#295
kranurag7 wants to merge 1 commit intomainfrom
kr/3414fea634256ae8

Conversation

@kranurag7
Copy link
Contributor

Edit tw.yaml in-place instead of overwriting it from melange.yaml.
This preserves fields like 'resources' that exist only in stereo's
tw.yaml.

Edit tw.yaml in-place instead of overwriting it from melange.yaml.
This preserves fields like 'resources' that exist only in stereo's
tw.yaml.
@kranurag7 kranurag7 requested review from rawlingsj and smoser February 4, 2026 17:43
Copy link
Contributor

@smoser smoser left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thoughts?

sed -e "1,10s/^\([ ]\+version\): .*/\1: \"${tag#v}\"/" \
debug 1 "updating tw.yaml in $gdir"
# update version, epoch, and expected-commit in-place in the existing tw.yaml
# this preserves any additional fields (like resources) that exist in stereo
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doing this would will lose any changes that we made in melange.yaml in tw.
this would include new subpackages or tests.

I view melange.yaml in this repo as the upstream file and tw.yaml is just to be written over by this.

that way when we add something to tw, we modify the melange.yaml to buidl and package it and then when we sync to wolfi it gets added.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants