summaryrefslogtreecommitdiff
path: root/dev-libs/libverto/metadata.xml
diff options
context:
space:
mode:
authorV3n3RiX <venerix@redcorelinux.org>2018-07-14 20:57:42 +0100
committerV3n3RiX <venerix@redcorelinux.org>2018-07-14 20:57:42 +0100
commit1798c4aeca70ac8d0a243684d6a798fbc65735f8 (patch)
treee48e19cb6fa03de18e1c63e1a93371b7ebc4eb56 /dev-libs/libverto/metadata.xml
parentd87262dd706fec50cd150aab3e93883b6337466d (diff)
gentoo resync : 14.07.2018
Diffstat (limited to 'dev-libs/libverto/metadata.xml')
-rw-r--r--dev-libs/libverto/metadata.xml15
1 files changed, 0 insertions, 15 deletions
diff --git a/dev-libs/libverto/metadata.xml b/dev-libs/libverto/metadata.xml
deleted file mode 100644
index 24304b1cca36..000000000000
--- a/dev-libs/libverto/metadata.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-<?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>