On 4/30/20 12:40 PM, josef Reidinger wrote: > [1] https://github.com/yast/yast-installation-control/pull/96
Checking the PR, I saw a diff from "disksize" to "string". That's right as there's no "disksize" data-type. We have also discussed that we should then modify our control.xml stored on disk during RPM-post-script (which is the right way as `zypper dup` is supported too). But I have a question: what happens in customers' AY profiles actually contain these "disksize" types? Are they going to be invalid? Should we replace/remove them when loading the profile first? I'd like to be careful here, because what used to be valid for ages now turns into invalid because of our internal change. That doesn't sound right even if our intentions were crystal clear. What do you think? Thx Lukas -- Lukas Ocilka, Systems Management Team Leader & YaST Product Owner SLE Department, SUSE Linux 🌲 Please consider the environment before printing this e-mail ☂ Handle with care - Your reply can be stored in the cloud 😱 Pie-chart is just a representation of randomly chosen data ⚠IMPORTANT: The contents of this email and any attachments are confidential. They are intended for the named recipient(s) only. If you have received this email by mistake, please, notify the sender immediately and do not disclose the contents to anyone or make copies of thereof. -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
