[zypp-devel] feedback/questions about zypp-evaporate
Hi , Just wanted to give some feedback/make some questions about zypp-evaporate. When machinery runs an inspection on a system we extract different scopes of information. 1. The list of packages `rpm -qa --qf ...` so we get the name, version, release, architecture, vendor and checksum of the package. 2. The list of repos `zypper --xmlout repos --details` so we get the alias, name, type, url, enabled, autorefresh, gpgcheck and priority. 3. The list of patterns `zypper patterns -i` so we capture name, version and release. Now if I compare this information in my system I go from having around 2445 packages to 266 solvables, which I find very cool btw. A use case for us would be the ability to * give zypper/zypp-evaportate from the command line a list of packages, repos and patterns from an inspected machine * optionally pass some flags to tell how to resolve in case of different scenarios and expected output format With this functionality we can improve the output of our kiwi export by making the config.xml file more concise (like in my case 10 fold shorter) Would this be possible? Thanks!
On Wednesday 24 February 2016 15:25:04 Mauro Morales wrote:
Hi ,
Just wanted to give some feedback/make some questions about zypp-evaporate.
When machinery runs an inspection on a system we extract different scopes of information.
1. The list of packages `rpm -qa --qf ...` so we get the name, version, release, architecture, vendor and checksum of the package. 2. The list of repos `zypper --xmlout repos --details` so we get the alias, name, type, url, enabled, autorefresh, gpgcheck and priority. 3. The list of patterns `zypper patterns -i` so we capture name, version and release.
Now if I compare this information in my system I go from having around 2445 packages to 266 solvables, which I find very cool btw. A use case for us would be the ability to
* give zypper/zypp-evaportate from the command line a list of packages, repos and patterns from an inspected machine
Evaporate needs to know all package dependencies. If you pass just the repos, evaporate will need to be able to access them in order to download and parse the metadata. It would be far easier, if you could create and pass a resolver testcase from this system? This would contain all necessary information without need to access any foreign repos.
* optionally pass some flags to tell how to resolve in case of different scenarios and expected output format
Which scenarios? At least different output formats is easy :) -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres SUSE LINUX GmbH, Development, ma@suse.com Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 74 053-0 +------------------------------------------------------------------+ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org To contact the owner, e-mail: zypp-devel+owner@opensuse.org
participants (2)
-
Mauro Morales -
Michael Andres