On Friday 22 June 2007 14:00:07 Jiri Srain wrote:
Hi! In order to allow workflows bound to patterns we need to extend the pattern definition on the media as well as the database and in-memory representation of a pattern. We need following tags:
I find the idea great, but the implementation propossal is really non-elegant (I don't have a better proposal)
"workflow_file" : string // file describing the workflow on the media "workflow_file_checksum" : the same as other checksums
what file is this? the workflow xml file?
"workflow_order" : string // to allow ordering, string for better extendibility
Yeah, I can see developers embeding YCP code in this string later. What is extendibility here then?
=Wkf =WkfCSum (if not specified in content file) =WkfOrd
What value does WkfOrd has? I still don't see YaST specific stuff being part of the pattern definition.
http://users.suse.cz/~locilka/PatternsAndAddOnsWithWorkflows/proposal-2007- 06-04.txt
I have one question, I imagine the use case, you have a mail-server pattern, and if it installed you want to start the mail-server workflow. How are you going to know either to start the postfix cfg workflow or the sendmail one, or [insert any supplied community module here] -- 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@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org