Closed #269.
--
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/issues/269#event-1800023513___
Rpm-maint mailing list
Meanwhile this patch adds a --queryformat modifier to generate UUID's from tag
values, which is an entirely orthogonal and mostly non-intrusive usage case
than converting hdrNum/tagNum to an octet string.
--
You are receiving this because you are subscribed to this thread.
Reply to this email
Changing indices to be octets (rather than integers) is a prerequisite to using
UUID's as a join key.
There are many problems (endianness, exposure of hdrNum/tagNum in the RPM API)
that need to be solved to use a UUID as an octet string for LMDB (and for BDB).
See other issues for
>From @n3npq:
> UUID's will be the starting point for a RPM+LMDB implementation used as
> header retrieval keys.
It didn't seem like you used this with the LMDB implementation
(ed9de1992f5e1c23e8d8dbd61325a1e0070f2c72), though you mention it as a starting
point. I'm guessing you're not
The rpm_uuid.patch is now applied to an RPM tree at
[https://github.com/rpm5/rpm/commit/c8c72fb195790dfa2d40c20ca597d9cc2b75](url)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
[rpm_uuid.patch.gz](https://github.com/rpm-software-management/rpm/files/1163437/rpm_uuid.patch.gz)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
UUID's provide a common format for identification and database retrieval.
The attached patch adds a header tag format to RPM queries.
- UUIDv1 time stamps (for events like build/install times):
```
$ ./rpm -q --qf '%{buildtime:uuidv1}\n' bash
c60fd500-bc0a-11e7-804e-003048b801de
```
- UUIDv3
