LIBSOLV-CONSTANTIDS(3)

💖 LIBSOLV-CONSTANTIDS — the libsolv manual, section 3 ✨

okay bestie, welcome to the fixed-Id hall of fame, this is libsolv-constantids from the LIBSOLV manual and it's lowkey the most organized page in the whole vibe 🌸

---

🎀 NAME 🎀

libsolv-constantids — fixed Ids for often used strings 💅

---

✨ DESCRIPTION ✨

so. Constant Ids are Ids of strings that come up constantly. They're defined so you can actually write code without losing your mind, and so the number of pool_str2id calls goes wayyy down. fr fr, that's the whole point.

These constant Ids are part of the binary ABI of libsolv. What that means: a minor version update will only ever add new constants, it will never change the existing Ids — compatibility stays intact, no cap. 👑

The on-disk solv format does not use the fixed Ids tho. It references the strings instead, so solv files can still be read even when the ABI is broken. iconic design tbh 🦋

---

🌈 SPECIAL STRINGS 🌈

• ID_EMPTY "" — the empty string, and it will always have Id 1. periodt.
• SYSTEM_SYSTEM "system:system" — the name of the always-installed "system" solvable. it's literally always there, main character energy 👑

---

🫶 SOLVABLE ATTRIBUTES 🫶

these are Ids for keynames of attributes. you use them in the lookup and storage functions to select the right attribute inside the solvable. and every description below is telling you the intended semantics of the values stored under that keyname, k? 💖

🌸 the core package info 🌸

• SOLVABLE_NAME "solvable:name" — the name of the package.
• SOLVABLE_ARCH "solvable:arch" — the architecture of the package. peep the Solvable Architecture section for the predefined architecture Id values.
• SOLVABLE_EVR "solvable:evr" — the version of the package. usually it's some combo of the Epoch, the Version, and the Release of the solvable.
• SOLVABLE_VENDOR "solvable:vendor" — a vendor string. usually whoever (company or group) built the binary package.

💅 dependency arrays (the gossip) 💅

• SOLVABLE_PROVIDES "solvable:provides" — an array of dependency Ids describing the capabilities this package provides.
• SOLVABLE_OBSOLETES "solvable:obsoletes" — an array of dependency Ids describing the packages this package replaces.
• SOLVABLE_CONFLICTS "solvable:conflicts" — an array of dependency Ids describing the capabilities this package conflicts with, i.e. the ones that can't be installed together with it. they do not get along, at all 💀
• SOLVABLE_REQUIRES "solvable:requires" — an array of dependency Ids describing the capabilities that must also be installed when this package is installed.
• SOLVABLE_RECOMMENDS "solvable:recommends" — an array of dependency Ids describing capabilities that should also be installed alongside this package. and no, it's not an error if not all of them can be met, breathe 🫶
• SOLVABLE_SUGGESTS "solvable:suggests" — an array of dependency Ids for capabilities that are also useful to have installed with this package. it's a lil hint to the user about other packages ✨
• SOLVABLE_SUPPLEMENTS "solvable:supplements" — an array of dependency Ids defining that this package should be installed if one of the capabilities is met. it's like recommends but running in reverse, the way that it works backwards is so cunty 🔥
• SOLVABLE_ENHANCES "solvable:enhances" — an array of dependency Ids defining that this package is useful to have installed if one of the capabilities is met. like suggests, but reversed. same energy, opposite direction 🦋

📝 text-y stuff 📝

• SOLVABLE_SUMMARY "solvable:summary" — should be a short string, no newlines, describing what the package does.
• SOLVABLE_DESCRIPTION "solvable:description" — a more verbose description of what the package does. it may be multiple lines, go off.
• SOLVABLE_DISTRIBUTION "solvable:distribution" — a short string describing the OS and OS version this package is built for.
• SOLVABLE_AUTHORS "solvable:authors" — a list of authors of this package. this attribute was used in SUSE packages.
• SOLVABLE_PACKAGER "solvable:packager" — the person who created the binary package. also check the vendor attribute, bestie.
• SOLVABLE_GROUP "solvable:group" — the package group this package belongs to. see also the keywords attribute.
• SOLVABLE_URL "solvable:url" — an URL pointing to more info about the package 🔗
• SOLVABLE_KEYWORDS "solvable:keywords" — list of keyword string IDs used for tagging this package.
• SOLVABLE_LICENSE "solvable:license" — the license(s) of this package.
• SOLVABLE_BUILDTIME "solvable:buildtime" — seconds since the unix epoch when the binary package was created.
• SOLVABLE_BUILDHOST "solvable:buildhost" — the name of the host where the binary package was created.
• SOLVABLE_EULA "solvable:eula" — if this attribute is present, the user should be asked to accept the end user license agreement before the package gets installed. read before you install, babe 📜
• SOLVABLE_CPEID "solvable:cpeid" — a Common Platform Enumeration string describing the platform this package is intended for. see also the distribution attribute.

🔔 messages 🔔

• SOLVABLE_MESSAGEINS "solvable:messageins" — a message to display to the user when the package gets installed.
• SOLVABLE_MESSAGEDEL "solvable:messagedel" — a message to display to the user when the package gets erased.

💾 sizes, files, times 💾

• SOLVABLE_INSTALLSIZE "solvable:installsize" — the disk space in bytes needed when installing the package.
• SOLVABLE_DISKUSAGE "solvable:diskusage" — a SUSE extension that stores, for each directory, the needed amount of disk space in kilobytes and inodes.
• SOLVABLE_FILELIST "solvable:filelist" — a list of files that the package contains.
• SOLVABLE_INSTALLTIME "solvable:installtime" — seconds since the unix epoch when the binary package was installed on the system.

📦 media / repo location 📦

• SOLVABLE_MEDIADIR "solvable:mediadir" — the directory on the repository that contains the package. if this attribute is set to void, the package architecture is used as the directory.
• SOLVABLE_MEDIAFILE "solvable:mediafile" — the filename on the repository that contains the package. if this attribute is set to void, the canonical file name of the package is used (i.e. a combination of the name, version, architecture).
• SOLVABLE_MEDIANR "solvable:medianr" — the media number, an integer saying which one of a multi-part media set this package is on.
• SOLVABLE_MEDIABASE "solvable:mediabase" — can be used to overwrite the repositories base url.
• SOLVABLE_DOWNLOADSIZE "solvable:downloadsize" — the size of the binary package in bytes.

🧬 source package info 🧬

• SOLVABLE_SOURCEARCH "solvable:sourcearch" — the architecture of the source package this package belongs to.
• SOLVABLE_SOURCENAME "solvable:sourcename" — the name of the source package this package belongs to. if set to void, the package name attribute is used instead.
• SOLVABLE_SOURCEEVR "solvable:sourceevr" — the version of the source package this package belongs to. if set to void, the package version attribute is used instead.

⚙️ triggers & checksums ⚙️

• SOLVABLE_TRIGGERS "solvable:triggers" — a list of package triggers for this package. used in the transaction ordering code.
• SOLVABLE_CHECKSUM "solvable:checksum" — the checksum of the binary package. see the Data Types section for the list of supported algorithms.
• SOLVABLE_PKGID "solvable:pkgid" — a string identifying a package. for rpm packages, this is the md5sum over the package header and the payload.
• SOLVABLE_HDRID "solvable:hdrid" — a string identifying a package. for rpm packages, this is the sha1sum over just the package header.
• SOLVABLE_LEADSIGID "solvable:leadsigid" — a string identifying the signature part of a package. for rpm packages, this is the md5sum from the start of the file up to the package header (i.e. it includes the lead, the signature header, and the padding).
• SOLVABLE_HEADEREND "solvable:headerend" — the offset of the payload in rpm binary packages. you can use this to download just the header when you wanna display info that isn't in the repository metadata. so smart honestly 🌟

📜 changelog 📜

• SOLVABLE_CHANGELOG "solvable:changelog" — the array containing all the changelog structures.
• SOLVABLE_CHANGELOG_AUTHOR "solvable:changelog:author" — the author of a changelog entry.
• SOLVABLE_CHANGELOG_TIME "solvable:changelog:time" — seconds since the unix epoch when the changelog entry was written.
• SOLVABLE_CHANGELOG_TEXT "solvable:changelog:text" — the text of a changelog entry.

---

and that's just the first batch, bestie — part 2 is loading 🔥🧚

✨ SPECIAL SOLVABLE ATTRIBUTES ✨

• RPM_RPMDBID "rpm:dbid" — the rpm database id of this (installed) package. Usually a small integer number. 💖
• SOLVABLE_PATCHCATEGORY "solvable:patchcategory" — the category field for patch solvables. Should be named “update:category” instead. like, the name is giving legacy, bestie 😭
• UPDATE_REBOOT "update:reboot" — if this attribute is present, the system should be rebooted after the update is installed. 🔥
• UPDATE_RESTART "update:restart" — if this attribute is present, the software manager should be run again after the update is installed. 🔄
• UPDATE_RELOGIN "update:relogin" — if this attribute is present, the user should log off and on again after the update is installed. 💅
• UPDATE_MESSAGE "update:message" — a message that should be shown to the user to warn him about anything non-standard. ⚠️
• UPDATE_SEVERITY "update:severity" — the severity of the update. 🚨
• UPDATE_RIGHTS "update:rights" — any legal or other rights of the update. ⚖️
• UPDATE_COLLECTION "update:collection" — the array containing the package list of the update. 📦
• UPDATE_COLLECTION_NAME "update:collection:name" — the name of the updated package. 🏷️
• UPDATE_COLLECTION_EVR "update:collection:evr" — the version of the updated package. 🔢
• UPDATE_COLLECTION_ARCH "update:collection:arch" — the architecture of the updated package. 🏗️
• UPDATE_COLLECTION_FILENAME "update:collection:filename" — the file name of the updated package. 📄
• UPDATE_REFERENCE "update:reference" — the array containing the reference list of the update. 📚
• UPDATE_REFERENCE_TYPE "update:reference:type" — the type of the reference, e.g. bugzilla. 🐞
• UPDATE_REFERENCE_HREF "update:reference:href" — the URL of the reference. 🔗
• UPDATE_REFERENCE_ID "update:reference:id" — the identification string of the reference, e.g. the bug number. 🆔
• UPDATE_REFERENCE_TITLE "update:reference:title" — the title of the reference, e.g. the bug summary. 📝
• PRODUCT_REFERENCEFILE "product:referencefile" — the basename of the product file in the package. 📁
• PRODUCT_SHORTLABEL "product:shortlabel" — an identification string of the product. 🏷️
• PRODUCT_DISTPRODUCT "product:distproduct" — Obsolete, do not use. Was a SUSE Code-10 product name. 💀
• PRODUCT_DISTVERSION "product:distversion" — Obsolete, do not use. Was a SUSE Code-10 product version. 💀
• PRODUCT_TYPE "product:type" — the type of the product, e.g. “base”. 👑
• PRODUCT_URL "product:url" — an array of product URLs. 🔗
• PRODUCT_URL_TYPE "product:url:type" — an array of product URL types. 🏷️
• PRODUCT_FLAGS "product:flags" — an array of product flags. 🚩
• PRODUCT_PRODUCTLINE "product:productline" — a product line string used for product registering. 🧵
• PRODUCT_REGISTER_TARGET "product:regtarget" — a target for product registering. 🎯
• PRODUCT_REGISTER_RELEASE "product:regrelease" — a release string for product registering. 🚀
• PUBKEY_KEYID "pubkey:keyid" — the keyid of a pubkey, consisting of 8 bytes in hex. 🔑
• PUBKEY_FINGERPRINT "pubkey:fingerprint" — the fingerprint of a pubkey, usually a sha1sum in hex. Old V3 RSA keys use a md5sum instead. 👆
• PUBKEY_EXPIRES "pubkey:expires" — the seconds since the unix epoch when the pubkey expires. ⏳
• PUBKEY_SUBKEYOF "pubkey:subkeyof" — the keyid of the master pubkey for subkeys. 👑
• PUBKEY_DATA "pubkey:data" — the MPI data of the pubkey. 🧬
• SOLVABLE_ISVISIBLE "solvable:isvisible" — an attribute describing if the package should be listed to the user or not. Used for SUSE patterns. 👀
• SOLVABLE_CATEGORY "solvable:category" — the category of a pattern. 🗂️
• SOLVABLE_INCLUDES "solvable:includes" — a list of other patterns that this pattern includes. 📥
• SOLVABLE_EXTENDS "solvable:extends" — a list of other patterns that this pattern extends. 📤
• SOLVABLE_ICON "solvable:icon" — the icon name of a pattern. 🎨
• SOLVABLE_ORDER "solvable:order" — an ordering clue of a pattern. 🔢
• SUSETAGS_SHARE_NAME "susetags:share:name" — Internal attribute to implement susetags shared records. Holds the name of the solvable used for sharing attributes. 🧩
• SUSETAGS_SHARE_EVR "susetags:share:evr" — Internal attribute to implement susetags shared records. Holds the version of the solvable used for sharing attributes. 🧩
• SUSETAGS_SHARE_ARCH "susetags:share:arch" — Internal attribute to implement susetags shared records. Holds the architecture of the solvable used for sharing attributes. 🧩

🏗️ SOLVABLE ARCHITECTURES 🏗️

okay so these are the predefined architecture values for commonly used architectures. no cap. ✨

• ARCH_SRC "src" — used for binary packages that contain the package sources. 📦
• ARCH_NOSRC "nosrc" — used for binary packages that contain some of the package sources, but not all files (because of restrictions). 🚫
• ARCH_NOARCH "noarch" — this package can be installed on any architecture. Used for rpm. 💅
• ARCH_ALL "all" — this package can be installed on any architecture. Used for Debian. 🐧
• ARCH_ANY "any" — this package can be installed on any architecture. Used for Archlinux and Haiku. 🌈

🔗 DEPENDENCY IDS 🔗

okay so namespaces are special modifiers that change the meaning of a dependency. Namespace dependencies are created with the REL_NAMESPACE flag. To make custom namespaces work you have to implement a namespace callback function. iykyk. ✨

The dependency markers partition the dependency array in two parts with different semantics. it's giving structural, bestie. 💅

• NAMESPACE_MODALIAS "namespace:modalias" — the dependency is a special modalias dependency that matches installed hardware. 🖥️
• NAMESPACE_SPLITPROVIDES "namespace:splitprovides" — the dependency is a special splitprovides dependency used to implement updates that include a package split. A splitprovides dependency contains a filename and a package name, it is matched if a package with the provided package name is installed that contains the filename. This namespace is implemented in libsolv, so you do not need a callback. 🧩
• NAMESPACE_LANGUAGE "namespace:language" — the dependency describes a language. The callback should return true if the language was selected by the user. 🗣️
• NAMESPACE_FILESYSTEM "namespace:filesystem" — the dependency describes a filesystem. The callback should return true if the filesystem is needed. 💾
• NAMESPACE_OTHERPROVIDERS "namespace:otherproviders" — this is a hack to allow self-conflicting packages. It is not needed with current rpm version, so do not use this namespace. 💀
• SOLVABLE_PREREQMARKER "solvable:prereqmarker" — this marker partitions the normal require dependencies from the prerequires. It is not needed for dependency solving, but it is used by the transaction ordering algorithm when a dependency cycle needs to be broken (non-prereq deps get broken first). 🔄
• SOLVABLE_FILEMARKER "solvable:filemarker" — this marker partitions the package provides dependencies from the synthetic file provides dependencies added by pool_addfileprovides(). 🗂️

🧬 DATA TYPES 🧬

okay so each attribute data is stored with a type, so that the lookup functions know how to interpret the data. The following types are available, bestie: ✨

• REPOKEY_TYPE_VOID "repokey:type:void" — no data is stored with this attribute. Thus you can only test if the attribute exists or not. Useful to store boolean values. 🫥
• REPOKEY_TYPE_CONSTANT "repokey:type:constant" — the data is a constant 32bit number. The number is stored in the key area, so using it does not cost extra storage space (but you need the extra key space). 🔢
• REPOKEY_TYPE_CONSTANTID "repokey:type:constantid" — the data is a constant Id. The Id is stored in the key area, so using it does not cost extra storage space (but you need the extra key space). 🆔
• REPOKEY_TYPE_ID "repokey:type:id" — the data is an Id. 🏷️
• REPOKEY_TYPE_NUM "repokey:type:num" — the data is an unsigned 64bit number. 🔢
• REPOKEY_TYPE_U32 "repokey:type:num32" — the data is an unsigned 32bit number. Obsolete, do not use. 💀
• REPOKEY_TYPE_DIR "repokey:type:dir" — the data is an Id of a directory. 📁
• REPOKEY_TYPE_STR "repokey:type:str" — the data is a regular string. 📝
• REPOKEY_TYPE_BINARY "repokey:type:binary" — the data is a binary blob. 🧬
• REPOKEY_TYPE_IDARRAY "repokey:type:idarray" — the data is an array of non-zero Ids. 🔢
• REPOKEY_TYPE_REL_IDARRAY "repokey:type:relidarray" — the data is an array of non-zero Ids ordered so that it needs less space. 📉
• REPOKEY_TYPE_DIRSTRARRAY "repokey:type:dirstrarray" — the data is a tuple consisting of a directory Id and a basename. Used to store file names. 📄
• REPOKEY_TYPE_DIRNUMNUMARRAY "repokey:type:dirnumnumarray" — the data is a triple consisting of a directory Id and two 32bit unsigned integers. Used to store disk usage information. 💽
• REPOKEY_TYPE_MD5 "repokey:type:md5" — the data is a binary md5sum. 🔐
• REPOKEY_TYPE_SHA1 "repokey:type:sha1" — the data is a binary sha1sum. 🔐
• REPOKEY_TYPE_SHA256 "repokey:type:sha256" — the data is a binary sha256sum. 🔐
• REPOKEY_TYPE_FIXARRAY "repokey:type:fixarray" — the data is an array of structures that have all the same layout (i.e. the same keynames and keytypes in the same order). 🧱
• REPOKEY_TYPE_FLEXARRAY "repokey:type:flexarray" — the data is an array of structures that have a different layout. 🌀
• REPOKEY_TYPE_DELETED "repokey:type:deleted" — the data does not exist. Used to mark an attribute that was deleted. 🗑️

💖 REPOSITORY METADATA 💖

Okay so these attributes are literally the meta info about the repository, bestie. Like the receipts for the whole vibe. 💅

• REPOSITORY_SOLVABLES "repository:solvables" — This one holds the array including all of the solvables. It's only used in the on-disk solv files, internally the solvables are stored in the pool’s solvable array for fast access. Periodt.
• REPOSITORY_DELTAINFO "repository:deltainfo" — This attribute holds the array including all of the delta packages. 🎀
• REPOSITORY_EXTERNAL "repository:external" — This attribute holds the array including all of the data to construct stub repodata areas to support on-demand loading of metadata. Lowkey iconic.
• REPOSITORY_KEYS "repository:keys" — This should really be named "repository:external:keys", ngl. It contains an array if Ids that consists of (keyname, keytype) pairs that describe the keys of the stub. 🙈
• REPOSITORY_LOCATION "repository:location" — This is used to provide a file name in the stub.
• REPOSITORY_ADDEDFILEPROVIDES "repository:addedfileprovides" — This attribute holds an array of filename Ids, that tell the library, that all of the Ids were already added to the solvable provides.
• REPOSITORY_RPMDBCOOKIE "repository:rpmdbcookie" — An attribute that stores a sha256sum over the file stats of the Packages database. It’s used to detect rebuilds of the database, as in that case the database Ids of every package are newly distributed.
• REPOSITORY_TIMESTAMP "repository:timestamp" — The seconds since the unix epoch when the repository was created. ⏰
• REPOSITORY_EXPIRE "repository:expire" — The seconds after the timestamp when the repository will expire.
• REPOSITORY_UPDATES "repository:updates" — An array of structures describing what this repository updates.
• REPOSITORY_DISTROS "repository:distros" — Also an array of structures describing what this repository updates. Seems to be the newer name of REPOSITORY_UPDATES. The way that naming is just… chaotic. 💀
• REPOSITORY_PRODUCT_LABEL "repository:product:label" — Should really be called "repository:updates:label". What distribution is updated with this repository.
• REPOSITORY_PRODUCT_CPEID "repository:product:cpeid" — The cpeid of the platform updated by this repository. Is both used in REPOSITORY_UPDATES and REPOSITORY_DISTROS to maximize confusion. And honestly? It ate. 😭
• REPOSITORY_REPOID "repository:repoid" — An array of Id strings describing keywords/tags about the repository itself.
• REPOSITORY_KEYWORDS "repository:keywords" — An array of Id strings describing keywords/tags about the content of the repository.
• REPOSITORY_REVISION "repository:revision" — An arbitrary string describing the revision of the repository.
• REPOSITORY_TOOLVERSION "repository:toolversion" — Some string describing somewhat the version of libsolv used to create the solv file. Cute.

---

✨ REPOSITORY METADATA FOR SUSETAGS REPOS ✨

These attributes describe repository files in a susetags repository. Let's get into it. 💖

• SUSETAGS_DATADIR "susetags:datadir" — The directory that contains the packages.
• SUSETAGS_DESCRDIR "susetags:descrdir" — The directory that contains the repository file resources.
• SUSETAGS_DEFAULTVENDOR "susetags:defaultvendor" — The default vendor used when a package does not specify a vendor.
• SUSETAGS_FILE "susetags:file" — An array of file resources of the repository.
• SUSETAGS_FILE_NAME "susetags:file:name" — The filename of the resource.
• SUSETAGS_FILE_TYPE "susetags:file:type" — The type of the resource, e.g. “META”.
• SUSETAGS_FILE_CHECKSUM "susetags:file:checksum" — The file checksum of the resource.

---

🌈 REPOSITORY METADATA FOR RPMMD REPOS 🌈

• REPOSITORY_REPOMD "repository:repomd" — An array of file resources of the repository.
• REPOSITORY_REPOMD_TYPE "repository:repomd:type" — The type of the resource, e.g. “primary”.
• REPOSITORY_REPOMD_LOCATION "repository:repomd:location" — The location (aka filename) of the resource
• REPOSITORY_REPOMD_TIMESTAMP "repository:repomd:timestamp" — The seconds since the unix epoch when the resource was created.
• REPOSITORY_REPOMD_CHECKSUM "repository:repomd:checksum" — The file checksum of the resource.
• REPOSITORY_REPOMD_OPENCHECKSUM "repository:repomd:openchecksum" — The checksum over the uncompressed contents of the resource.
• REPOSITORY_REPOMD_SIZE "repository:repomd:size" — The size of the resource file.

---

🦋 DELTA PACKAGE ATTRIBUTES 🦋

• DELTA_PACKAGE_NAME "delta:pkgname" — The target package name for the delta package. Applying the delta will recreate the target package.
• DELTA_PACKAGE_EVR "delta:pkgevr" — The version of the target package.
• DELTA_PACKAGE_ARCH "delta:pkgarch" — The architecture of the target package.
• DELTA_LOCATION_DIR "delta:locdir" — The directory in the repository that contains the delta package.
• DELTA_LOCATION_NAME "delta:locname" — The first part of the file name of the delta package.
• DELTA_LOCATION_EVR "delta:locevr" — The version part of the file name of the delta package.
• DELTA_LOCATION_SUFFIX "delta:locsuffix" — The suffix part of the file name of the delta package.
• DELTA_LOCATION_BASE "delta:locbase" — This attribute can be used to overwrite the repositories base url for the delta.
• DELTA_DOWNLOADSIZE "delta:downloadsize" — The size of the delta rpm file.
• DELTA_CHECKSUM "delta:checksum" — The checksum of the delta rpm file.
• DELTA_BASE_EVR "delta:baseevr" — The version of the package the delta was built against.
• DELTA_SEQ_NAME "delta:seqname" — The first part of the delta sequence, the base package name.
• DELTA_SEQ_EVR "delta:seqevr" — The evr part of the delta sequence, the base package evr. Identical to the DELTA_BASE_EVR attribute.
• DELTA_SEQ_NUM "delta:seqnum" — The last part of the delta sequence, the content selection string.

---

👑 AUTHOR 👑

Michael Schroeder <mls@suse.de> — the icon, the legend, the moment. 💖

---

This whole masterpiece is from libsolv, dated 03/02/2022, and it's the LIBSOLV-CONSTANTIDS(3) page. No cap, it ate. ✨💅