[Yum-devel] Xtrigger and package structures

Menno Smits menno-yum at freshfoo.com
Thu Sep 16 08:16:33 UTC 2004

Hash: SHA1

seth vidal wrote:
| On Sun, 2004-09-05 at 00:55, Menno Smits wrote:
|>How do we go from here with the XTrigger work? Should I wait for you to
|>provide the data structures to pass in to the XTrigger class or do you
|>want me to have a try at this? My yum internals knowledge is still
|>minimal but this might be a good way for me to start learning.
| I posted a transactioninfo.py with a set of classes in them - anticipate
| that being close to what yum may pass to XTrigger.

Saw those. They looked good for the usage cases that I can think of.

| Anticipate it will also pass where in the process yum is (pre-trans,
| post-trans, pre-package-trans, post-package-trans)

Fine. That's already accounted for.

| In the case of pre-package and post-package it will should also include
| a unique indentifier of which package is being acted on.

Do you want to pass the unique package identifier as an extra parameter
to XTrigger.run() or pass it inside the transaction structure? Perhaps
there should be a root object which acts as a container for transaction
structure you've already proposed. This root object could hold extra
info about the transaction such as this unique ID for the "active" package.

| However, I've been thinking about about the pre-package-trans and
| post-package-trans and I'm trying to figure out a situation where it'd
| be useful to run something there that's not already covered by the
| pre-trans and post-trans.

I can't think of much either. In almost all cases the RPM should take of
most of this type of stuff itself. It's probably worth having the
support there though.


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


Scanned by the NetBox from NetBox Blue

More information about the Yum-devel mailing list