diff options
author | V3n3RiX <venerix@redcorelinux.org> | 2017-10-09 18:53:29 +0100 |
---|---|---|
committer | V3n3RiX <venerix@redcorelinux.org> | 2017-10-09 18:53:29 +0100 |
commit | 4f2d7949f03e1c198bc888f2d05f421d35c57e21 (patch) | |
tree | ba5f07bf3f9d22d82e54a462313f5d244036c768 /dev-libs/libassuan/metadata.xml |
reinit the tree, so we can have metadata
Diffstat (limited to 'dev-libs/libassuan/metadata.xml')
-rw-r--r-- | dev-libs/libassuan/metadata.xml | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/dev-libs/libassuan/metadata.xml b/dev-libs/libassuan/metadata.xml new file mode 100644 index 000000000000..fe0789259056 --- /dev/null +++ b/dev-libs/libassuan/metadata.xml @@ -0,0 +1,19 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd"> +<pkgmetadata> +<maintainer type="project"> + <email>crypto@gentoo.org</email> + <name>Crypto</name> +</maintainer> +<longdescription> +In an ideal world, Assuan is irrelevant. Assuan's primary use is to +allow a client to interact with a non-persistent server. Using Assuan, +this is accomplished by forking a subprocess and communicating with it +via, for example, a pipe or unix domain socket. This method is neither +elegant nor efficient especially when there is a lot of data spread +across several transactions: not only is there a penalty for an +increased number of context switches, but also a significant amount of +data is MEMCPYed from the client to a file descriptor and from the file +descriptor to the server. +</longdescription> +</pkgmetadata> |