From: "Maciej Barć" <xgqt@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-lang/fennel/
Date: Tue, 1 Feb 2022 22:23:19 +0000 (UTC) [thread overview]
Message-ID: <1643754197.0541586e78354f24d34c5cc21763ad8275890041.xgqt@gentoo> (raw)
commit: 0541586e78354f24d34c5cc21763ad8275890041
Author: Maciej Barć <xgqt <AT> gentoo <DOT> org>
AuthorDate: Tue Feb 1 22:22:56 2022 +0000
Commit: Maciej Barć <xgqt <AT> gentoo <DOT> org>
CommitDate: Tue Feb 1 22:23:17 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0541586e
dev-lang/fennel: update metadata
Package-Manager: Portage-3.0.30, Repoman-3.0.3
Signed-off-by: Maciej Barć <xgqt <AT> gentoo.org>
dev-lang/fennel/metadata.xml | 16 +++++-----------
1 file changed, 5 insertions(+), 11 deletions(-)
diff --git a/dev-lang/fennel/metadata.xml b/dev-lang/fennel/metadata.xml
index 2b5cd319731f..001e74a2f442 100644
--- a/dev-lang/fennel/metadata.xml
+++ b/dev-lang/fennel/metadata.xml
@@ -6,24 +6,18 @@
<email>xgqt@gentoo.org</email>
<name>Maciej Barć</name>
</maintainer>
- <longdescription lang="en">
+ <longdescription>
Fennel is a lisp that compiles to Lua. It aims to be easy to use,
expressive, and has almost zero overhead compared to handwritten Lua.
-
- - Full Lua compatibility - You can use any function or library from Lua.
- - Zero overhead - Compiled code should be just as or more efficient
+ Full Lua compatibility - You can use any function or library from Lua.
+ Zero overhead - Compiled code should be just as or more efficient
than hand-written Lua.
- - Compile-time macros - Ship compiled code with no runtime dependency
+ Compile-time macros - Ship compiled code with no runtime dependency
on Fennel.
- - Embeddable - Fennel is a one-file library as well as an executable.
+ Embeddable - Fennel is a one-file library as well as an executable.
Embed it in other programs to support runtime extensibility and
interactive development.
-
At https://fennel-lang.org there's a live in-browser REPL you can use
without installing anything.
</longdescription>
- <upstream>
- <bugs-to>https://github.com/bakpakin/Fennel/issues</bugs-to>
- <remote-id type="github">bakpakin/Fennel</remote-id>
- </upstream>
</pkgmetadata>
next reply other threads:[~2022-02-01 22:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 22:23 Maciej Barć [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-28 15:00 [gentoo-commits] repo/gentoo:master commit in: dev-lang/fennel/ Maciej Barć
2024-06-27 22:42 Maciej Barć
2024-04-13 22:56 Maciej Barć
2024-02-24 21:50 Maciej Barć
2024-01-30 19:58 Maciej Barć
2024-01-30 19:58 Maciej Barć
2024-01-21 7:58 Viorel Munteanu
2024-01-15 3:32 Ionen Wolkens
2023-12-14 4:15 Sam James
2023-09-16 14:48 Maciej Barć
2023-09-02 14:30 Maciej Barć
2023-07-10 18:56 Maciej Barć
2023-07-10 18:56 Maciej Barć
2023-05-15 19:33 Maciej Barć
2023-05-06 9:59 Arthur Zamarin
2023-02-14 10:42 Maciej Barć
2023-02-14 10:42 Maciej Barć
2023-02-14 10:42 Maciej Barć
2023-01-21 9:22 Arthur Zamarin
2022-10-17 2:13 Maciej Barć
2022-10-17 2:13 Maciej Barć
2022-08-29 2:38 Maciej Barć
2022-08-29 2:38 Maciej Barć
2022-08-14 20:06 Sam James
2022-04-16 16:29 Maciej Barć
2022-02-01 22:23 Maciej Barć
2021-11-28 18:27 Maciej Barć
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1643754197.0541586e78354f24d34c5cc21763ad8275890041.xgqt@gentoo \
--to=xgqt@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox