Martin, This one was a bit more delayed to be implemented ;)
I've managed to de-obsolete patches where dependencies weren't included into the patchdiag.xref so now PCA should really be happy with the output.. Can you check also to have a second-brain view on that ? Regards, Thomas On Tue, 31 Jan 2012 16:16:37 +0100 Martin Paul <[email protected]> wrote: > > - populating the xref > > - Assume only one rev (the last used in dependencies) is present > > per patch > > - Removing any obsolete flag and "Obsoleted by:" text inside the > > synopsis. > > > > Correct? > > Yup, think so. > > > I can also do it this way... I got all the info I need, I can even > > imagine to allow the user to choose which method is the best for him > > Yes, at the end having an option would probably be best. > > > Like if you would apply the 10 Recommended patch cluster without > > downloading every single patch which is in it. You simply could > > generate xref from the list of patches it contains and then run pca > > against this xref... wouldn't that be a wonderful world ? > > The basic design of Sun's patching design using patchdiag.xref really > isn't (or wasn't) all that bad. Besides just having one current > master xref file, one can put it to good use which such custom xref > files; Sun, with the access to all the patch metadata could've done > wonderful things. Alone the fact that one can use a "frozen" copy of > an xref file to put a certain patching milestone on any given machine > even months later is a great thing, used by many. It's just sad that > all this has an expiration date on it since Solaris 11 and IPS > appeared. > > Martin. > -- Thomas Gouverneur _____ _ | ____|___ _ __ (_)_ __ | _| / __| '_ \| \ \/ / | |___\__ \ |_) | |> < |_____|___/ .__/|_/_/\_\ Network |_| SPRL TVA: BE6836018011 T: +32 498 23 00 40 W: http://espix.net M: <[email protected]>
