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
I'd like a cekit sub-command that output some kind of structured information that described the image descriptor and module inter-dependencies. e.g. (spitballing)
Cekit's module dependency system is quite sophisticated and there are some subleties that make figuring out precise module dependencies quite tricky:
a module may depend upon a module name which is provided by more than one other module
sometimes this is resolved by module versions
various other corner-cases
As an image maintainer, it's sometimes necessary to map out which images depend on what modules, and what modules depend on others, to understand the impact of proposed changes.
Attempting to resolve this outside of cekit, effectively duplicating cekit's module-dependency logic, runs the risk of missing a subtlety and therefore generating misleading information. Adding a command such as this inside cekit ensures the output will correspond exactly to Cekit's module-dependency-resolution logic, even as it changes over time.
Next steps
I'd be grateful if the first step was a ACK/NACK on the concept, and then we can get into the weeds of implementation design. I'm happy to get involved in implementing this, but it's been some time since I've hacked on Cekit to any significant extent.
The text was updated successfully, but these errors were encountered:
Describe the solution you'd like
I'd like a cekit sub-command that output some kind of structured information that described the image descriptor and module inter-dependencies. e.g. (spitballing)
A suitable format might be Graphviz's
dot
language, e.g.resulting in (when procssed by
dot
):I guess cekit could (optionally) also invoke
dot
, so something likeperhaps.
Additional context
Cekit's module dependency system is quite sophisticated and there are some subleties that make figuring out precise module dependencies quite tricky:
As an image maintainer, it's sometimes necessary to map out which images depend on what modules, and what modules depend on others, to understand the impact of proposed changes.
Attempting to resolve this outside of cekit, effectively duplicating cekit's module-dependency logic, runs the risk of missing a subtlety and therefore generating misleading information. Adding a command such as this inside cekit ensures the output will correspond exactly to Cekit's module-dependency-resolution logic, even as it changes over time.
Next steps
I'd be grateful if the first step was a ACK/NACK on the concept, and then we can get into the weeds of implementation design. I'm happy to get involved in implementing this, but it's been some time since I've hacked on Cekit to any significant extent.
The text was updated successfully, but these errors were encountered: