diff options
| author | V3n3RiX <venerix@redcorelinux.org> | 2018-07-14 21:03:06 +0100 |
|---|---|---|
| committer | V3n3RiX <venerix@redcorelinux.org> | 2018-07-14 21:03:06 +0100 |
| commit | 8376ef56580626e9c0f796d5b85b53a0a1c7d5f5 (patch) | |
| tree | 7681bbd4e8b05407772df40a4bf04cbbc8afc3fa /dev-libs/libverto/metadata.xml | |
| parent | 30a9caf154332f12ca60756e1b75d2f0e3e1822d (diff) | |
gentoo resync : 14.07.2018
Diffstat (limited to 'dev-libs/libverto/metadata.xml')
| -rw-r--r-- | dev-libs/libverto/metadata.xml | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/dev-libs/libverto/metadata.xml b/dev-libs/libverto/metadata.xml new file mode 100644 index 000000000000..24304b1cca36 --- /dev/null +++ b/dev-libs/libverto/metadata.xml @@ -0,0 +1,15 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd"> +<pkgmetadata> +<longdescription lang="en">Many applications and libraries are unable to write asynchronous code because they are unable to pick an event loop. This is particularly true of libraries who want to be useful to many applications who use loops that do not integrate with one another or which use home-grown loops. libverto provides a loop-neutral async api which allows the library to expose asynchronous interfaces and offload the choice of the main loop to the application.</longdescription> +<maintainer type="person"> + <email>eras@gentoo.org</email> + <name>Eray Aslan</name> +</maintainer> +<use> + <flag name="glib">Support event loops using <pkg>dev-libs/glib</pkg></flag> + <flag name="libev">Support event loops using <pkg>dev-libs/libev</pkg></flag> + <flag name="libevent">Support event loops using <pkg>dev-libs/libevent</pkg></flag> + <flag name="tevent">Support event loops using <pkg>sys-libs/tevent</pkg></flag> +</use> +</pkgmetadata> |