Hi hackers, while redesigning various parts of libzypp a question has been raised about incosistencies/misdesign we currently have in our YUM metadata extensions and ZYpp regarding patches. INTRO: In metadata, a patch includes atoms: element atoms { (element-package | element-script | element-message)+ }+ and the package element is an extension of a normal yum:package: element-package = element yum:package { package & element-pkgfiles & (element license-to-confirm { localized-string }?) } where pkgfiles are the delta, patch or plain rpm file data. In libzypp, delta and patch rpms are appended to Package which, basically represents a plain rpm package resolvable. The rest of the /patch/atoms/package data is an Atom resolvable (with its own dependencies), a helper resolvable used to resolve patch dependencies. PROBLEMS: Well, for me as writer of the new YUMParser it is just a question of mapping the data to classes in libzypp (ResolvableData). Experienced zypp hackers can add more... SUGGESTIONS: ? Attaching current version of patch.rnc and patch.rng for convenience. See also: http://en.opensuse.org/Libzypp/Patches/Rationale http://en.opensuse.org/Libzypp/Metadata/repomd/patches (not very informative today, but will be expanded) Cheers, Jano -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org