[Yum-devel] Xtrigger and package structures

Menno Smits menno-yum at freshfoo.com
Wed Sep 1 22:31:25 UTC 2004


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Seth,

No problems on the delayed response. I've been busy on other stuff too.
I'm still keen to proceed with this.

seth vidal wrote:
| What if I could hand back a structure something like:
|
| package
|     current_state
|     transaction_process
|     transaction_reason
|     future_state
|     name
|     arch
|     epoch
|     ver
|     rel
|     repository (installed if in the rpmdb)
....
| What do you think?

The structures you propose look good and should work nicely for the pre
and post (per package) transaction functionality. What about the more
global operations that would run, for example, before any package
updates are run (eg. diplaying a prompt if more than N packages are to
be removed)? Would you see yum just passing XTrigger a list of all
package objects for all updates to be performed?

Based on what you've showed me it seems I should possibly be renaming
the "state" parameter of XTrigger.run() to "stage" instead to avoid
confusion with the package states.

regards,
Menno


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBNk28WH92Dls5JXwRAr94AJ9l846WpOC75ivQeyfmQaTAyxPAvACdGXHH
ZAHUH8n6Mq7PzpIfpzkDBXc=
=TS20
-----END PGP SIGNATURE-----

Scanned by the NetBox from NetBox Blue
(http://netboxblue.com/)




More information about the Yum-devel mailing list