Hi Mike, Yes accumulation is well known and identified as biggest patch releasing issue and solution is simple - use dependancy to full extent and use mutual dependancy , no revisions at all - and it is not too hard to resolve from tools point of view.
Well, real multi-patching was huge step forward from sequential patching we have before, as well as all new super fast dependency check. This was however side effect of zone-patching. The reason why it happen was zone patching and were introduced under that umbrella. Introduced in 4 months FYI. - Return codes, I raise this question about 6 months ago explaining that single return code does not work for set of patches and asked to discuss and to see what API needed - I receive no replay. - Patchadd -t was introduced as internal option for QA to let them reprogram some test. And it is not working with zones - never intended because it is passing pdo and directly call old script instead. - Text output - see my answer on return codes, I thought XML may be good, but it seems it is not really needed. No replays. - Unfortunately pdo was not picked up by higher level tools yet and so they use old kshell script. Try patchadd directly (patchadd -M dir) without -t and i should work faster. - Prepatch scripts must be used only for special cases very rare. Currently they are overused, unfortunately. I am author of pdo.c - it was programmed from zero in four months and I have also new pdo with recursive patching and new Solaris upgrade algorythm, will be nice if someone pick it up after me. I have no idea that it is not opened - remember I had special thread about how pdo works etc. But I do not even know who made that desicion - not to open this code and why it was made. May be it is too complicated? I is very funny to have my full comments in that thread and don't have code itself... vassun This message posted from opensolaris.org
