Dne pátek 22 červen 2007 14:30 Michael Andres napsal(a):
On Fri, Jun 22, 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:
"workflow_file" : string // file describing the workflow on the media "workflow_file_checksum" : the same as other checksums "workflow_order" : string // to allow ordering, string for better extendibility
(the names can be adapted to fit attribute naming schema)
The suggestions for the SuSEtags metadata format are
=Wkf =WkfCSum (if not specified in content file) =WkfOrd
ZYPP is not required to process this data anyhow (maybe except the checksum?), all that's needed is to deliver the data to YaST. The update of package bindings will be trivial.
- But why putting this into the pattern definition? Why not one (separate) file that maps pattern<->workflow, but spreading it across several locations?
It is an option as well. But thhere must be a binding between a pattern and itw workflow and it must be possible to define it in all our supported metadata formats. That's the only requirement.
- workflow_file and workflow_file_checksum must appear in the content file anyway.
Otherwise we had to parse all the patterns to see whether a workflow file changed and we must refresh. And changing the workflow would require reloading the pattern (because of the changed checksum)
Right, but if a new workflow is added, you have to modify the pattern in the database anyway, since the workflow is a part of a pattern the very same way as packages the pattern should drag in. Jiri -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.cz Lihovarska 1060/12 tel: +420 284 028 959 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz