Mailinglist Archive: zypp-devel (116 mails)

[Duncan Mac-Vicar Prett <dmacvicar@xxxxxxx>]

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 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)

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).

-- 
Duncan Mac-Vicar Prett  
Novell :: SUSE R&D, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx