Duncan Mac-Vicar Prett wrote:
On Friday 22 June 2007 15:54:27 Lukas Ocilka wrote:
Workflow for packages was never wanted and might be added later. Currently we support only Add-Ons Products and Patterns.
So we do it in a hacky way resolvable kind per resolvable kind. What will you do when we have to support it with packages?
It's actually not a "hacky" way, but the "way of minimal changes". What I wanted was a minimal change to libzypp and pkg-bindings just to have the wanted feature. The only changes I need are: * Support =Wkf: in libzypp and pkg-binding * Support =WkfOrd: in libzypp and pkg-bindings We wanted it in 10.3, a super-generic workflow handling might work nice too but that wouldn't be before 11.0.
It has to be a clean way to trigger the workflow after *any* event has happened. As I said the idea is great and can improve user experience, but you are relating workflow to patterns (which have no relation, because you never know what a pattern adds) and because you are doing a second "solving" at YaST level (very similar to how selections were handled before)
The wery same way as, e.g., running a 'yast2 http-server' does, checks whether required packages are installed.
For example, I gave the example of the mail server. The solution is to see what package did the pattern install, that is a second (simpler solve), instead of letting the package itself trigger a workflow.
Languages? If a special language is installed, you might want to trigger a workflow to configure fonts and input methods.
A Pattern can install another pattern, and another pattern, and so on. So a pattern by itself can't trigger the workflow (except if it pulls the workflow by itself).
I see your point, it's really interesting, but is libzypp-team able to do it now? It would also need implementing special callbacks in pkg-bindings. Please, talk to Klaus first. Lukas