Greats,
I need some clarification about packages states and relations between
packages in a transaction :
As far as I've understood, each package as a state in the transaction, and
some attributes are populated depending on the state
(updates,obsoletes,relatedto,...).
I saw that (most of the time ?) when a package has the state TS_UPDATE, the
updates attributes is populated with the package list that this package
update (generally juste one package, the same one with a lower version).
But I've discovered that this is not always true, when updating yum on
RHEL5, some other packages are updated too and this is what I get :
yum-metadata-parser:
state=TS_UPDATE
updates,obsoletes and relatedto attributes are empty
yum:
state=TS_UPDATE
updates contains the old yum installed package
relatedto contains [(('yum','noarch','0','3.0.1','5.el5'),'updates')]
I stop here the package list.
Why is the behavior not the same for the state TS_UPDATE ?
I need a way to know exactly wich packages are installed and wich packages
are removed for my plugin, when a say packages, it's the (n,a,e,v,r) tuple.
In the case of an update for example :
- removed packages:
('yum','noarch','0','3.0.1','5.el5')
- installed packages:
('yum','noarch','0','3.2.8','9.el5_2.8')
It's really not easy to develop a plugin for yum because of its youth:
It lacks of documentation, the behavior of some functions are changing (for
example YumBase.doGenericSetup(), what is needed by UpdateMetadata(), ...)
and some functions are called inappropriately (for example
searchPackageByNevra that does not need Nevra but Naevr)
However, I hope that it will continue to improve.
Have a nice day
--
View this message in context:
http://www.nabble.com/-plugin--yum-packages-transaction-tp18010946p18010946.html
Sent from the YUM - Dev mailing list archive at Nabble.com.
_______________________________________________
Yum-devel mailing list
[email protected]
https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
