man.bsd.lv manual page server

Manual Page Search Parameters
PKG_PRINTF(3) Library Functions Manual PKG_PRINTF(3)

pkg_printf, pkg_fprintf, pkg_dprintf, pkg_snprintf, pkg_asprintf, pkg_utstring_printf, pkg_vprintf, pkg_vfprintf, pkg_vdprintf, pkg_vsnprintf, pkg_vasprintf, pkg_utstring_vprintf — formatted output of package data

library “libpkg”

#include <pkg.h>

int
pkg_printf(const char * restrict format, ...);

int
pkg_fprintf(FILE * restrict stream, const char * restrict format, ...);

int
pkg_dprintf(int fd, const char * restrict format, ...);

int
pkg_snprintf(char * restrict str, size_t size, const char * restrict format, ...);

int
pkg_asprintf(char **ret, const char * restrict format, ...);

struct utstring *
pkg_utstring_printf(struct utstring * restrict utstring, const char * restrict format, ...);

#include <stdarg.h>

int
pkg_vprintf(const char * restrict format, va_list ap);

int
pkg_vfprintf(FILE * restrict stream, const char * restrict format, va_list ap);

int
pkg_vdprintf(int fd, const char * restrict format, va_list ap);

int
pkg_vsnprintf(char * restrict str, size_t size, const char * restrict format, va_list ap);

int
pkg_vasprintf(char **ret, const char * restrict format, va_list ap);

struct utstring *
pkg_utstring_vprintf(struct utstring * restrict utstring, const char * restrict format, va_list ap);

The () family of functions produces output of package data according to a format as described below, analogously to the similarly named printf(3) family of functions. The pkg_printf() and () functions write output to stdout, the standard output stream; () and () write output to the given output stream; () and () write output to the given file descriptor; pkg_snprintf() and pkg_vsnprintf() write to the character string str; pkg_asprintf() and pkg_vasprintf() dynamically allocate a new string with malloc(3) to write to; pkg_utstring_printf() and pkg_utstring_vprintf() write to the given utstring structure.

These functions write the output under the control of a format string that specifies how subsequent arguments (or arguments accessed via the variable-length argument facilities of stdarg(3)) are converted for output.

These functions return the number of characters printed (not including the trailing ‘\0’ used to end output to strings) or a negative value if an output error occurs, except for () or () which return the number of characters that would have been printed if the size were unlimited (again, not including the final ‘\0’) and the two functions () and () which return the given utstring pointer, or NULL in the case of errors.

The () and () functions set *ret to be a pointer to a buffer sufficiently large to hold the formatted string. This pointer should be passed to free(3) to release the allocated storage when it is no longer needed. If sufficient space cannot be allocated, pkg_asprintf() and pkg_vasprintf() will return -1 and set ret to be a NULL pointer.

The () and () functions will write at most size-1 of the characters printed into the output string (the size'th character then gets the terminating ‘\0’); if the return value is greater than or equal to the size argument, the string was too short and some of the printed characters were discarded. The output is always null-terminated.

The format string is composed of zero or more directives: ordinary characters (not %), which are copied unchanged to the output stream; and conversion specifications, each of which results in fetching zero or more subsequent arguments. Each conversion specification is introduced by the % character. The arguments must correspond properly with the conversion specifier. After the %, the following appear in sequence:

Humanized number conversions scale the number to lie within the range 1 - 1000 (power of ten conversions using the ? format modifier) or 1 - 1024 (power of two conversions using the # format modifier) and append a scale factor as follows:

The SI power of ten suffixes are

1
1,000
1,000,000
1,000,000,000
1,000,000,000,000
1,000,000,000,000,000
1,000,000,000,000,000,000

The IEE/IEC (and now also SI) power of two suffixes are:

1
1,024
1,048,576
1,073,741,824
1,099,511,627,776
1,125,899,906,842,624
1,152,921,504,606,846,976

Format codes will format the output classified as the type shown in square brackets. %I is unique in that it can only be used inside a “row format.” All other format codes may be used stand-alone. When used in this fashion they will consume one argument of the indicated type from the function's argument list.

The array valued format codes (A, B, C, D, F, G, L, O, U, d, and r) and the timestamp format code (t) can be followed by a “row format”. They will use a default row format (detailed below) if one is not given explicitly.

The row format is bracketed by the character sequences %{ and %} and, for array values only, may be optionally divided into two by the character sequence %|. For array values, it contains one or two strings containing any number of a context sensitive subset of format conversions from those described here. For timestamp values it contains any number of format conversion specifiers with meanings as described in strftime(3).

The first or only format string is repeatedly processed for each of the array items in turn. The optional second format string is processed as a separator between each of the array items. If no row format is given, output will be generated according to a default format, detailed below.

Within a “row format” string, you may use any of the single-character non-array valued format codes except for %S, but only the two-character format codes which correspond to the parent item and have the same first character. Array valued format codes may not be used within row formats, nor may you embed one “row format” within another. Only one argument, a struct pkg * pointer is consumed from the argument list. Thus this is a legal format string:

"%B%{%n-%v:%Bn%|\n%}"

which serves to print out a list of the shared libraries required by the programs within the package, each prefixed by the package name and version.

The conversion specifiers and their meanings are:

%A
Annotations [array] struct pkg *

Default row format %A%{%An: %Av\n%|%}

%An
Annotation tag name [string] struct pkg_note *
%Av
Annotation value [string] struct pkg_note *
%B
Required shared libraries [array] struct pkg *

Default row format: %B%{%Bn\n%|%}

Required shared library name [string] struct pkg_shlib *
Categories [array] struct pkg *

Default row format: %C%{%Cn%|, %}

Category name [string] struct pkg_category *
%D
Directories [array] struct pkg *

Default row format: %D%{%Dn\n%|%}

Directory ownership: group name [string] struct pkg_dir *
Directory path name [string] struct pkg_dir *
Directory permissions [mode] struct pkg_dir *
Directory ownership: user name [string] struct pkg_dir *
Files [array] struct pkg *

Default row format: %F%{%Fn\n%|%}

File ownership: group name [string] struct pkg_file *
File path name [string] struct pkg_file *
File permissions [mode] struct pkg_file *
File SHA256 checksum [string] struct pkg_file *
File ownership: user name [string] struct pkg_file *
Groups [array] struct pkg *

Default row format: %G%{%Gn\n%|%}

Group name [string] struct pkg_group *
%I
Row counter [integer].

This format code may only be used as part of a “row format.”

Licenses [array] struct pkg *

Default row format: %L%{%Ln%| %l %}

Licence name [string] struct pkg_license *
Package message [string] struct pkg *
Repository identity [string] struct pkg *
%O
Options [array] struct pkg *

Default row format: %O%{%On %Ov\n%|%}

Option name [string] struct pkg_option *
Option value [string] struct pkg_option *
Option default value [string] (if known: will produce an empty string if not.) struct pkg_option *
Option description [string] (if known: will produce an empty string if not.) struct pkg_option *
%R
Repository path - the path relative to the repository root that package may be downloaded from [string]. struct pkg *
%S
Arbitrary character string [string] const char *
%U
Users [array] struct pkg *

Default row format: %U%{%Un\n%|%}

User name [string] struct pkg_user *
%V
Old version [string]. Valid only during operations when one version of a package is being replaced by another. struct pkg *
Autoremove flag [boolean] struct pkg *
%b
Provided shared libraries [array] struct pkg *

Default row format: %b%{%bn\n%|%}

Provided shared library name [string] struct pkg_shlib *
Comment [string] struct pkg *
Dependencies [array] struct pkg *

Default row format: %d%{%dn-%dv\n%|%}

Dependency lock status [boolean] struct pkg_dep *
Dependency name [string] struct pkg_dep *
Dependency origin [string] struct pkg_dep *
Dependency version [string] struct pkg_dep *
Description [string] struct pkg *
Additional information [string] struct pkg *
Locking status [boolean] struct pkg *
License logic [licence-logic] struct pkg *
Maintainer [string] struct pkg *
Package name [string] struct pkg *
Origin [string] struct pkg *
Prefix [string] struct pkg *
Requirements [array] struct pkg *

Default row format: %r%{%rn-%rv\n%|%}

Requirement lock status [boolean] struct pkg_dep *
Requirement name [string] struct pkg_dep *
Requirement origin [string] struct pkg_dep *
Requirement version [string] struct pkg_dep *
Package flat size [integer] struct pkg *
Installation timestamp [date-time] struct pkg *
Package checksum [string] struct pkg *
Package version [string] struct pkg *
Home page URL [string] struct pkg *
Package tarball size [integer] struct pkg *
Package short checksum [string] struct pkg *
A ‘%’ is written. No argument is converted. The complete conversion specification is ‘%%’.

The decimal point character is defined in the program's locale (category LC_NUMERIC).

In no case does a non-existent or small field width cause truncation of a numeric field; if the result of a conversion is wider than the field width, the field is expanded to contain the conversion result.

Effective format modifiers:

First Alternate Form: 0 if the array is empty, 1 if it has any number of elements within it
Second Alternate Form: The number of elements in the array

Effective format modifiers:

-
Left align

Effective format modifiers:

-
Left align
First Alternate Form: humanized number (decimal)
Second Alternate Form: humanized number (binary)
Zero pad
‘ ’
Blank for plus
Explicit + or - sign
‘'’
Thousands separator

The two possible values ‘true’ or ‘false’ may be output in one of three different styles: plain; or alternate forms 1 and 2 specified using format modifiers.

no
yes (*)
The second alternate form produces no output for false.

Effective format modifiers:

First Alternate Form
Second Alternate Form
-
Left align

The file mode is a bitmap representing setid, user, group and other permissions. The plain format prints it as an octal value, for example:

4755

The first alternate form is similar but adds a leading zero:

04755

Whilst the second alternate form produces a string in the style of strmode(3):

-rwsr-xr-x

Note: there is always a space at the end of the strmode(3) output.

Effective format modifiers (all forms):

-
Left align

Additionally, when the value is printed as an integer (i.e., plain or alternate form 1), these additional modifiers take effect:

First Alternate Form: add leading zero to octal integer
Zero pad

License-logic is a three-valued type: one of ‘SINGLE’, ‘OR’ or ‘AND’, which shows whether the package is distributed under the terms of a single license, or when there are several applicable licenses, whether these should be treated as alternatives or applied in aggregate. There are three different output styles: plain; or alternate forms 1 and 2 specified using format modifiers.

==
| ||
& &&

Effective format modifiers:

First Alternate Form
Second Alternate Form
-
Left align

When used outside of a “row format” string may be followed by an optional strftime(3) format, enclosed in %{ and %}, which will be used to format the timestamp. Otherwise the timestamp is printed as an integer value of the number of seconds since the Epoch (00:00:00 UTC, 1 January 1970; see time(3).)

Effective format modifiers:

-
Left align

Additionally, when the value is printed as an integer (i.e., without strftime(3) format codes enclosed in %{ and %}, the following format modifiers are also effective:

First Alternate Form: humanized number (decimal)
Second Alternate Form: humanized number (binary)
Zero pad
‘ ’
Blank for plus
Explicit + or - sign
‘'’
Thousands separator

To print the package installation timestamp in the form “Sunday, July 3, 10:02”,

#include <pkg.h>
pkg_fprintf(stdout, "%t%{%A, %B %e, %R%}\n", pkg);

To print the package name and version, followed by the name and version of all of the packages it depends upon, one per line, each indented by one tab stop:

#include <pkg.h>
pkg_printf("%n-%v\n%d%{\t%dn-%dv%|%\n%}\n", pkg, pkg, pkg);

Note that the item separator part of the row format is only printed between individual row items. Thus to fill the character array buf with a one-line string listing all of the licenses for the package separated by “and” or “or” as appropriate:

#include <pkg.h>
char buf[256];
pkg_snprintf(buf, sizeof(buf), "%L%{%Ln%| %l %}", pkg);

In addition to the errors documented for the write(2) system call, the pkg_printf() family of functions may fail if:

[]
An invalid wide character code was encountered.
[]
Insufficient storage space is available.

printf(1), printf(3), strftime(3), setlocale(3) pkg_repos(3), pkg-repository(5), pkg.conf(5), pkg(8), pkg-add(8), pkg-annotate(8), pkg-audit(8), pkg-autoremove(8), pkg-backup(8), pkg-check(8), pkg-clean(8), pkg-config(8), pkg-convert(8), pkg-create(8), pkg-delete(8), pkg-fetch(8), pkg-info(8), pkg-install(8), pkg-lock(8), pkg-query(8), pkg-register(8), pkg-repo(8), pkg-rquery(8), pkg-search(8), pkg-set(8), pkg-shell(8), pkg-shlib(8), pkg-ssh(8), pkg-stats(8), pkg-update(8), pkg-updating(8), pkg-upgrade(8), pkg-version(8), pkg-which(8)

The pkg_printf family of functions do not correctly handle multibyte characters in the format argument.

There is no way to sort the output of array valued items.

Equivalents to the sprintf() and vsprintf() functions are not supplied. Instead, use pkg_snprintf() to write into a fixed length buffer without danger of overflow.

The pkg_printf() family, like the printf() family of functions it is modelled on, is also easily misused in a manner allowing malicious users to arbitrarily change a running program's functionality by either causing the program to print potentially sensitive data “left on the stack”, or causing it to generate a memory fault or bus error by dereferencing an invalid pointer.

Programmers are therefore strongly advised to never pass untrusted strings as the format argument, as an attacker can put format specifiers in the string to mangle your stack, leading to a possible security hole. This holds true even if the string was built using a function like snprintf(), as the resulting string may still contain user-supplied conversion specifiers for later interpolation by pkg_printf().

Always use the proper secure idiom:

pkg_snprintf(buffer, sizeof(buffer), "%s", string);
August 15, 2015 DragonFly-5.6.1