dev-scheme/racket: update metadata.xml

untabify & add bugs-to

Signed-off-by: Maciej Barć <xgqt@riseup.net>
This commit is contained in:
Maciej Barć 2021-07-20 18:42:03 +02:00
parent be322d5934
commit 37977b04d5
No known key found for this signature in database
GPG Key ID: 031C9FE65BED714A

View File

@ -1,39 +1,41 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
<maintainer type="person">
<email>xgqt@protonmail.com</email>
<name>Maciej Barć</name>
</maintainer>
<longdescription lang="en">
Racket's interactive mode encourages experimentation, and quick scripts
easily compose into larger systems. Small scripts and large systems both
benefit from native-code JIT compilation. When a system gets too big to
keep in your head, you can add static types.
Extend Racket whenever you need to. Mold it to better suit your tasks
without sacrificing interoperability with existing libraries and without
having to modify the tool chain. When less is more, you can remove parts
of a language or start over and build a new one.
Whether you're just starting out, want to know more about programming
language applications or models, looking to expand your horizons, or
ready to dive into research, Racket can help you become a better
programmer and system builder.
</longdescription>
<use>
<flag name="chez">
Build Racket on Chez (Racket CS)
</flag>
<flag name="futures">
Enable racket/future library for fine-grained hardware parallelism
</flag>
<flag name="places">
Enable racket/place library for share-nothing parallelism and message-passing communication. Compared to futures, places are heavyweight, but they have a simpler performance model.
</flag>
<flag name="threads">
Enable support for green threads
</flag>
</use>
<upstream>
<remote-id type="github">racket/racket</remote-id>
</upstream>
<maintainer type="person">
<email>xgqt@protonmail.com</email>
<name>Maciej Barć</name>
</maintainer>
<longdescription lang="en">
Racket's interactive mode encourages experimentation, and quick scripts
easily compose into larger systems. Small scripts and large systems both
benefit from native-code JIT compilation. When a system gets too big to
keep in your head, you can add static types.
Extend Racket whenever you need to. Mold it to better suit your tasks
without sacrificing interoperability with existing libraries and without
having to modify the tool chain. When less is more, you can remove parts
of a language or start over and build a new one.
Whether you're just starting out, want to know more about programming
language applications or models, looking to expand your horizons, or
ready to dive into research, Racket can help you become a better
programmer and system builder.
</longdescription>
<use>
<flag name="chez">
Build Racket on Chez (Racket CS)
</flag>
<flag name="futures">
Enable racket/future library for fine-grained hardware parallelism
</flag>
<flag name="places">
Enable racket/place library for share-nothing parallelism and message-passing communication. Compared to futures, places are heavyweight, but they have a simpler performance model.
</flag>
<flag name="threads">
Enable support for green threads
</flag>
</use>
<upstream>
<bugs-to>https://github.com/racket/racket</bugs-to>
<remote-id type="github">racket/racket</remote-id>
</upstream>
</pkgmetadata>