mirrors/guru
1
0
Fork 0
mirror of https://github.com/gentoo-mirror/guru.git synced 2026-07-20 20:43:09 -04:00
Code Issues Packages Projects Releases Wiki Activity

dev-ml/*: improve metadata

Browse Source 
Signed-off-by: Alessandro Barbieri <lssndrbarbieri@gmail.com>
This commit is contained in:
Alessandro Barbieri
2022-04-26 12:32:34 +02:00
parent 7613b95df7
commit 8ba1e8a9c8
97 changed files with 1522 additions and 652 deletions
Download Patch File Download Diff File Expand all files Collapse all files

41
dev-ml/mirage-profile/metadata.xml
View File

@@ -1,15 +1,34 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
<maintainer type="person">
<email>lssndrbarbieri@gmail.com</email>
<name>Alessandro Barbieri</name>
</maintainer>
<upstream>
<remote-id type="github">mirage/mirage-profile</remote-id>
</upstream>
<use>
<flag name="unix">Adds a Unix backend collector</flag>
<!--<flag name="xen">Adds a Xen MirageOS backend collector</flag>-->
</use>
<maintainer type="person">
<email>lssndrbarbieri@gmail.com</email>
<name>Alessandro Barbieri</name>
</maintainer>
<use>
<flag name="unix">Adds a Unix backend collector</flag>
<!--<flag name="xen">Adds a Xen MirageOS backend collector</flag>-->
</use>
<longdescription lang="en">This library can be used to trace execution of OCaml/Lwt programs (such as
Mirage unikernels) at the level of Lwt threads. The traces can be viewed using
JavaScript or GTK viewers provided by [mirage-trace-viewer][] or processed by
tools supporting the [Common Trace Format (CTF)][ctf]. Some example traces can
be found in the blog post [Visualising an Asynchronous
Monad](http://roscidus.com/blog/blog/2014/10/27/visualising-an-asynchronous-monad/).
Libraries can use the functions mirage-profile provides to annotate the traces
with extra information. When compiled against a normal version of Lwt,
mirage-profile's functions are null-ops (or call the underlying untraced
operation, as appropriate) and OCaml's cross-module inlining will optimise
these calls away, meaning there should be no overhead in the non-profiling
case.</longdescription>
<upstream>
<doc>https://mirage.github.io/mirage-profile/</doc>
<bugs-to>https://github.com/mirage/mirage-profile/issues</bugs-to>
<remote-id type="github">mirage/mirage-profile</remote-id>
<maintainer>
<name>Thomas Leonard</name>
<email>talex5@gmail.com</email>
</maintainer>
</upstream>
</pkgmetadata>