Mailinglist Archive: zypp-devel (115 mails)

[Lukas Ocilka <lukas.ocilka@xxxxxxx>]

Lukas Ocilka wrote:
> So, about the current solution:
> Every single resolvable can have its own workflow (pattern, language,
> product, package...). All these pieces of information also with the
> order of workflows are written into single XML file for one product
> (URL). Libzypp parses the file and if any resolvable having its own
> workflow is either selected or unselected to be installed or removed
> from the pool, libzypp useses a callback to YaST via package-bindings.
> YaST then operates with the workflow itself and libzypp doesn't care.
> 
> What is it good for?
> - It solves all possible resolvables at once
> - Callbacks can be redefined without touching libzypp
> - YaST doesn't need to use any hacks for querying which resolvables were
>   changes and which of them have a workflow etc.
> 
> See the attached proposal (changed and old one) or see this link:
> http://users.suse.cz/~locilka/PatternsAndAddOnsWithWorkflows/
> 
> Anyway, we need a manager's blessing for such change of proposal :)
> because now more things would be implemented in libzypp then I first
> expected.

OK, so it seems that nobody has objected against the proposal which
probably means that it is widely accepted.

When is this going to happen? What does zypp-team need from me? Who will
implement it in libzypp?

Thanks & Bye
Lukas

-- 

Lukas Ocilka, YaST Developer                     (xn--luk-gla45d)
-----------------------------------------------------------------
SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic