You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
component versions need to be settable during override-build , just like a snap. Currently it fails with the following error
RuntimeError: 'override-build' in part 'nvidia-550-ko-comp' executed an invalid control API call: variable 'version' can be set only once.
Why it needs to get done
components need to be able to dynamically set their version based on revision numbers and other system settings. This is not possible if the version has to be hardcoded into the version field.
The text was updated successfully, but these errors were encountered:
This is because the part is decoupled from the component, this would need to be a new craftctl command specific to the component that takes a component name and the desired version, or overload the current set version command to use a key=value (component=version) like syntax.
Or @lengau's suggestion craftctl set comp1.version=<value>.
After discussing with @sergiusens and @cmatsuoka, this is unlikely to be completed this cycle. Claudio is going to discuss this proposal with Gustavo tomorrow.
What needs to get done
component versions need to be settable during override-build , just like a snap. Currently it fails with the following error
RuntimeError: 'override-build' in part 'nvidia-550-ko-comp' executed an invalid control API call: variable 'version' can be set only once.
Why it needs to get done
components need to be able to dynamically set their version based on revision numbers and other system settings. This is not possible if the version has to be hardcoded into the version field.
The text was updated successfully, but these errors were encountered: