[Rpm-maint] [rpm-software-management/rpm] Add support for private user data in transaction elements (#1366)

Panu Matilainen notifications at github.com
Mon Sep 21 07:44:31 UTC 2020


The "key" passed to rpmtsAddInstallEleemnt() and associated with transaction
elements is sometimes mistaken for user data, but it is not, as rpm relies
on it having a very specific meaning and is passed around with that very
assumption.

API users have all sorts of (legit!) needs, lets add a proper private user
data member to transaction elements.

The Python bindings to this are kinda dangerous if you liberally mix Python
and C as we can't know whether the pointer is an actual Python object or not
so we can only assume it is and hope for the best. Nobody in their right
mind should be setting user data from one language and accessing it from
another, really...
You can view, comment on, or merge this pull request online at:

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

-- Commit Summary --

  * Add support for private user data in transaction elements

-- File Changes --

    M lib/rpmte.c (12)
    M lib/rpmte.h (14)
    M python/rpmte-py.c (30)
    M tests/rpmpython.at (14)

-- Patch Links --

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

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1366
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20200921/189c6c99/attachment.html>


More information about the Rpm-maint mailing list