[Rpm-maint] [rpm] Add RPMCALLBACK_ELEM_PROGRESS callback type (#36)

Michal Domonkos notifications at github.com
Tue Dec 8 17:45:22 UTC 2015


Currently, there's no callback type that would be issued per each
transaction element.  RPMCALLBACK_TRANS_ST* are only issued during the
prepare phase but not when packages are actually installed or erased.
Likewise, RPMCALLBACK_INST_ST* and RPMCALLBACK_UNINST_ST* won't be
issued if an install or erase operation is skipped for some reason (a
script or a package upgrade failure).

Having such a callback would allow the Python API consumers to properly
track the currently processed element.  This is important since not
every callback type carries enough data about the subject package; while
the INST types provide the user object passed to a former addInstall
call, the UNINST types only provide the package name (which may not be
unique within the transaction set).

This commit adds such a callback, that is issued every time a new
element from the set is about to be processed.
You can view, comment on, or merge this pull request online at:

  https://github.com/rpm-software-management/rpm/pull/36

-- Commit Summary --

  * Add RPMCALLBACK_ELEM_PROGRESS callback type

-- File Changes --

    M lib/rpmcallback.h (1)
    M lib/transaction.c (4)
    M python/rpmmodule.c (1)

-- Patch Links --

https://github.com/rpm-software-management/rpm/pull/36.patch
https://github.com/rpm-software-management/rpm/pull/36.diff

---
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/36
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20151208/9cb8d1c6/attachment.html>


More information about the Rpm-maint mailing list