METALINK_FILE_T(3)
π metalink_file_t(3) β libmetalink Manual π
β¨ NAME β¨
okay so bestie, welcome to the metalink_file_t(3) page from the libmetalink Manual. This one is literally:
metalink_file_t β The structure that holds information of a single file. periodt π
πΈ SYNOPSIS πΈ
#include <metalink/metalink_types.h>
π¦ DESCRIPTION π¦
metalink_file_t is a structure that holds information of a single file. It contains an array of URLs (metalink_resource_t(3)), checksums and metadata for a file. Thatβs the whole main-character job, and it ate. π
π STRUCTURE MEMBERS π
Hereβs the struct in all its glory, copied exactly so you can trust the vibe check:
char *name;
long long int size;
char *version;
char *language;
char *os;
metalink_resource_t **resources;
int maxconnections;
metalink_checksum_t **checksums;
metalink_chunk_checksum_t *chunk_checksum;
π·οΈ name
Null terminated file name of the resource which corresponds to name element in Metalink XML file. Cute, direct, does what it says. β¨
π size
Length of the resource in bytes. Thatβs it, thatβs the number. π
π version
Null terminated version string which corresponds to version element in Metalink XML file. Iconic little string behavior. π
π£οΈ language
Null terminated language string which corresponds to language element in Metalink XML file. She speaks fluent Metalink XML. π
π» os
Null terminated os string which corresponds to os element in Metalink XML file. Okay bestie, tell us the operating system. π
π resources
Null terminated array of pointer of metalink_resource_t(3) structure. This corresponds to resources element in Metalink XML file. Each metalink_resource_t(3) structure corresponds to url element in Metalink XML file. So many links, so much slay. π¦
π¦ maxconnections
This is a value of maxconnections attribute of file element. This value is usually used for upper limit of concurrent connections for the resource. Ngl, itβs the βhow many at onceβ number. π₯
π§Ύ checksums
Null terminated array of pointer of metalink_checksum_t(3) structure. This field is an array because in Metalink specification, verification element can contain multiple hash elements. Each metalink_checksum_t(3) structure corresponds to hash element in Metalink XML file. Multiple hashes? Obsessed. π
π§© chunk_checksum
The chunk checksum(aka piece hash) for the resource. This corresponds to pieces element under verification element in Metalink XML file. Tiny pieces, big checksum energy. π
π SEE ALSO π
go read these next, bestie, iykyk π«Ά
xoxo, your libmetalink bestie π β this page is from libmetalink 0.0.3, dated 10/25/2008. π
π¦ where this page comes from
- epel 9: libmetalink-devel 0.1.3-24.el9 Β· MIT
- opensuse-leap 16.0: libmetalink-devel 0.1.3-160000.2.2 Β· MIT
- opensuse-leap 16.0: libmetalink-devel 0.1.3-160000.2.2 Β· MIT
- opensuse-leap 16.0: libmetalink-devel 0.1.3-160000.2.2 Β· MIT
- opensuse-leap 16.0: libmetalink-devel 0.1.3-160000.2.2 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms