On Tuesday 22 May 2007 17:03:28 you wrote:
Well, seeing it from one angle (the implementation), yes. But in my mind patches not only consist of the set of dependencies, but also of the immediate deps itself (or rather also of the differences between the installed stuff and the new version, no matter if those differences actually exist as delta rpm or if they exist only conceptually). So my mental model of patches is a blob of dependencies and some file deltas, where the file deltas is the more important part. But I guess it's not important how my mental model is. It doesn't help nor hinder their implementation as actual rpms.
Actually they are just metadata that depends on newer rpms. The fact that some of these rpms can be installed downloading delta/patch rpms is something evaluated at commit time and not at solving time, thus the patch does not need to know about rpms at all, it only need to express which version of a group of packages fixes the problem. The commit logic should grab and rpm and install it, or download a script and run it to patch a binary, or get a delta rpm, or untar something in /. So the file delta is just an implementation detail, but it is not in the patch itself. Note: in our current metadata it is, but just because the patch format is missdesigned. They not need to be there (therefore all packages are duplicated inside the patch and the primary file!!) -- Duncan Mac-Vicar Prett Novell :: SUSE R&D, Maxfeldstr. 5, 90409 Nürnberg GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org