Mailinglist Archive: zypp-devel (115 mails)

[Lukas Ocilka <lukas.ocilka@xxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michael Andres wrote:
> On Mon, Jul 02, 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
> 
> IMO "No". 
> 
> - Libzypp can assist maintaining an uptodate copy of the workflow file on 
> disk. 
> 
> - Libzypp provides information about items being installed/removed (we may 
> enhance if the current state is not sufficient).
> 
> But IMO libzypp should not process the xml. That's YaST (maybe 
> pkg-bindings) stuff.

IMO "Yes".

There are two types of XML use here:

1.) Definition which workflow is assigned to which resolvable. Such as,
    package 'apache2.rpm' with workflow 'http-server-apache'.
2.) The XML workflow, such as 'http-server-apache.xml'

Libzypp triggers:
Callback::SelectedResolvable (`package, apache2, http-server-apache)
YaST downloads 'http-server-apache.xml', parses and caches it.

The first definition needs to be kept up-to-date by libzypp because if
it was done by YaST itself, YaST would have to cache all first-type XML
files whenever a repository is added and it would have to refresh it
whenever the file is changed (which is a bit tricky, for instance, when
the file is either on not-inserted CD or on a remote repository with
network down).

Of course, only the first-type XML will be kept up-to-date by libzypp,
the second-type is downloaded by YaST after the Callback is triggered.

Bye
Lukas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFGkpDDVSqMdRCqTiwRAoGMAKCNDMsfDYEoREocceQ345gvPNLgFgCeL61o
9AjLadK4wF5RzlvZHujEmGY=
=p8Rz
-----END PGP SIGNATURE-----
-- 
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx