Age | Commit message (Collapse) | Author | Files | Lines |
|
- None of these are true enum uses as the value typically originates
from python integers etc.
|
|
|
|
|
|
|
|
|
|
- Similarly to the build-bindings, permit import failures as librpmsign
might not be installed and we dont want to force the dependencies
into every single installation
|
|
Make the source header visible to python code.
|
|
- Just one leftover offender in the form of forgotten type rename
from commit 675bfca5cc300105f7859f028cc00ea036e72966
|
|
- We /could/ of course add a getter for this but ... sorry folks, what
rpm happens to use as buildroot internally isn't anybody elses
business.
|
|
- Whee, for a change more lines removed than added...
|
|
|
|
- Leaving the painful and somewhat pointless exercise of changing
all the Package and Source references for another rainy day
|
|
- These huge structs have no business being visible to the public.
Just brute-force split all remaining spec internal structures into
another internal header, including where needed.
- The only thing accessing these structs outside of librpmbuild is
the python spec bindings. Temporarily permit direct access to
rpmspec_internal.h until we have the necessary API in place.
|
|
- Other than seeing "does it compile", statically linked python
extensions make no sense as they're unusable to python.
|
|
- Conditionalize the python subdir on toplevel make instead of
python subdir makefile.
|
|
|
|
- Eliminate uses of "class" which is a reserved keyword in C++
|
|
- Instead of masking and bitfiddling all over the place, use the
new getters to get the exact (enum) type directly. rpmTagGetType()
is now unused within rpm but leaving around for backwards compatibility
|
|
- The preferred flags default would be RPMSPEC_NONE, but it would break
compatibility with older rpm versions where rpm.spec() doesn't accept
flags.
|
|
- This is mostly just a toy for now, but serves as a kind of yardstick
for what is missing in librpmbuild to be generally useful for
building stuff.
|
|
|
|
- librpmbuild actually now has what remotely resembles an API, after
we broke every single thing there was ;)
|
|
|
|
- The whole rootDir seems dubious for build purposes, but in any case its
only relevant during the actual build process, not for spec parsing.
Set spec->rootDir from buildSpec() for the duration of the
build to avoid having to refactor doScript() and all right now.
|
|
- braindamage from commit fab2debfe440d677dbd072c3cd73d2c99876e7a5,
causing list index out of range for any non-versioned dependency
and bogus garbage for the rest, doh...
|
|
- rpmdsNew() returns NULL if the requested dependency type doesn't
exist in the header. The C-side API can handle NULL to all rpmds
"methods" and this is how librpm deals with non-existent sets rather
than waste memory on for empty ds structures. However the python side
wasn't expecting NULL for legal requests (but not setting error either)
and thus blowing up with SystemError exception.
- Raise TypeError on illegal arguments to rpm.ds constructor, and present
non-existent dependency sets as empty rpm.ds objects to python. This
lets python callers use iteration over ds items regardless of whether
the dependency actually exists or not. The alternative of returning
None (or raising exceptions) would break existing code for no
particularly good reason.
|
|
- This seems to be a de-facto standard in python land, as rpm.version
hasn't been in any released version we can still change this easily.
Suggestion from James Antill.
|
|
- this has never been used for anything at all, there are better things
to use our memory for than unused arrays
|
|
- Buildtime was never part of rpm version comparison nor should it be,
on rpm level the only sensible differentiator between two identical
dependencies is the dependency color if any. Other than that, random()
just as "appropriate" as build time.
|
|
- this was never used by upstream at least, and the "patch rpms" this
refers to was abandoned by Suse in favor of deltarpm a long time ago...
|
|
- Rpm has never done anything useful with "BuildRequires(prep): foo"
style dependencies other than recorded them in src.rpms, nor is there much
point in properly supporting this in the future either
- Frees up four more bits from rpmsenseFlags for better uses
|
|
- the naming between header/rpmte/rpmds "instance" is wonderfully
inconsistent... oh well
|
|
|
|
- pkgNEVR in problems is now always the NEVR of the transaction element
triggering the problem, and altNEVR is the other affected package,
dependency string is stored in the problem string attribute
- no user visible changed, except for somebody crazy enough to try to
do something other than print the problem message strings
- we wouldn't really need to strdup() the pkgNEVR in problems now,
but leaving that alone for the moment...
|
|
|
|
|
|
|
|
- Objects supporting __len__() use (len > 0) for boolean representation,
which normally makes sense but as the match iterator count is often
zero despite the iterator actually existing and returning something,
and breaks existing code (rpmlint at least)
- Adding a __bool__() (known as __nonzero__() in Python < 3) method
returning true for non-NULL iterator fixes this and gives more
meaningful answers than pre 4.8.0 which simply always returned True
|
|
- get the debug messages out of API, this is what should've been in commit
dbdbe8010cd944f026a5a4e5d071eb31d29d81c4
|
|
- get the debug messages out of API, this is what should've been in commit
dbdbe8010cd944f026a5a4e5d071eb31d29d81c4
|
|
|
|
|
|
|
|
|
|
|
|
- its not useful outside the ordering internals and API users have no
business messing with it
|
|
- it's really the C-side that needs this, doing it in C avoids nasty
surprises when subclassing rpm.ts
- partial revert of commit 92d18d1d7139b37065ea742cfe0e8cee5e9c3500
|
|
- the python object holds reference to header here, decref the header
so it gets freed eventually
|
|
- PyList_Append() bumps the object reference count, callers need to
explicitly decref them... oops :)
|
|
|