Eu arriscaria adivinhar que os mapeamentos do repositório são manipulados por zypper , assim como yum , em vez de rpm . Além disso, a questão que você ligou em sua própria pergunta mostra que yumdb é usado para essa finalidade dentro do Fedora, o que apoiaria minha suposição aqui. A documentação do OpenSUSE revela:
test RPM XML Metadata format is mostly used for online repositories on the internet. It has its origins in the YUM package manager.
Just lately it was extended to support repositories split across multiple media.
Consulte o código fonte da especificação de esquema do zypper do OpenSUSE no github . Embora os metadados façam parte do pacote rpm , ele está sendo usado por yum / zypper (independentemente) ou se a ferramenta rpm faz ter essa capacidade incorporada, as informações do banco de dados não são compartilhadas entre yum < - > rpm e / ou zypper < - > rpm .
Depois de ler a totalidade da sua pergunta, eu não tenho certeza se você é o usuário final que deseja trabalhar com o zypperdb (?) ou se você é um desenvolvedor que quer construir rpm packages. Para este último, como evitei anteriormente, as informações podem ser especificadas em um arquivo rpm spec .
rpm metadata
This is an XML format for describing the critical metadata from an rpm package for dependency resolving and installation. Currently, this format is supported by apt-rpm,smartpm,red carpet and yum.
The files break down as follows:
repomd.xml this is the file that describes the other metadata files. It is like an index file to point to the other files. It contains timestamps and checksums for the other files. This lets a client download this one, small file and know if anything else has changed. This also means that cryptographically (ex: gpg) signing this one file can ensure repository integrity.
primary.xml.[gz] this file stores the primary metadata information. This includes information such as:
name, epoch, version, release, architecture
file size, file location, description, summary, format, checksums header byte-ranges, etc.
- dependencies, provides, conflicts, obsoletes, suggests, recommends
- file lists for the package for CERTAIN files - specifically files matching: /etc*, bin/, /usr/lib/sendmail [1]
- filelists.xml.[gz] this file stores the complete file and directory listings for the packages. The package is identified by: name, epoch, version, release, architecture and package checksum id.
- other.xml.[gz] this file currently only stores the changelog data from packages. However, this file could be used for any other additional metadata that could be useful for clients.
- groups.xml.[gz] this file is tentatively described. The intention is for a common package-groups specification as well. There is still some sections for this format that need to be fleshed out.
FIXME The specification needs better and more current documentation and needs to be included here. :)