[Yum-devel] Xtrigger and package structures

seth vidal skvidal at phy.duke.edu
Wed Sep 1 06:15:43 UTC 2004


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)


so if you were installing the package foo and it had a dependency on bar
you'd get a list of these package objects:

foo
  current_state = uninstalled
  transaction_process = install
  transaction_reason = 'user requested'
  future_state = installed
  name = foo
  arch = noarch
  epoch = 0
  ver = 1
  rel = 1
  repository = myrepo

bar
  current_state = uninstalled
  transaction_process = install
  transaction_reason = 'dependency'
  future_state = installed
  name = bar
  arch = noarch
  epoch = 0
  ver = 1
  rel = 2
  repository = myrepo


and if we were updating the package baz we'd get:

baz
  current_state = uninstalled
  transaction_process = update
  transaction_reason = 'user requested'
  future_state = installed
  name = baz
  arch = noarch
  epoch = 0
  ver = 1
  rel = 2
  repository = myrepo

baz
  current_state = installed
  transaction_process = update
  transaction_reason = 'user requested'
  future_state = uninstalled
  name = baz
  arch = noarch
  epoch = 0
  ver = 1
  rel = 1
  repository = rpmdb


essentially,we'd be passing much of the data in the tsInfo class - but
in a slightly nicer structure - something i should consider for that
class anyway. :)

What do you think?

-sv





More information about the Yum-devel mailing list