Um, nevermind, sort of. I've discovered that if I use rpmtsCheck() first (optional for rpmgraph), the final order is the same as rpm chooses at the cmd line. If anybody can give a conceptual explanation of why this is, I'd find it helpful. Thanks again. -Aaron > -----Original Message----- > From: rpm-list-bounces@xxxxxxxxxx > [mailto:rpm-list-bounces@xxxxxxxxxx] On Behalf Of Aaron Hanson > Sent: Thursday, December 08, 2005 3:42 PM > To: RPM Package Manager > Subject: rpmtsOrder() > > Hi All - > > I'm trying to figure out how to use this method, using > the 'rpmgraph' tool as an example. I want to know what order > rpm will use to install a large list of packages before I > actually do the installation. > But rpmgraph doesn't come up with the same sequence as rpm at > the command-line. Any thoughts? Suggestions on how to interpret the > rpmteTree() and rpmteDepth() fields of a transaction element > might help; I'm guessing that to make a flat list, Depth is > subordinate to Tree... > > Thanks. > > -Aaron > > _______________________________________________ > Rpm-list mailing list > Rpm-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/rpm-list > _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
