On 11/07/2014 05:09 PM, James Antill wrote:
It's inside yum, after the transaction runs, in a function called verifyTransaction(). The two main parts of it are making sure that each transaction member that was supposed to be installed was actually installed (and dito. for those that were supposed to be removed), and installing/removing the yumdb information.
OK. Sounds good to me for testing purposes to make sure that code is all right. But why we have this in production code? -- Miroslav Suchy, RHCE, RHCDS Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys _______________________________________________ Yum-devel mailing list Yum-devel@lists.baseurl.org http://lists.baseurl.org/mailman/listinfo/yum-devel