From: "Michael Palimaka" <kensington@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-lisp/c2ffi/
Date: Wed, 15 May 2019 11:37:49 +0000 (UTC) [thread overview]
Message-ID: <1557920257.8af3a0782b735703438a02928d1ec8126c2dfaa0.kensington@gentoo> (raw)
commit: 8af3a0782b735703438a02928d1ec8126c2dfaa0
Author: Harald Judt <h.judt <AT> gmx <DOT> at>
AuthorDate: Tue May 14 09:36:12 2019 +0000
Commit: Michael Palimaka <kensington <AT> gentoo <DOT> org>
CommitDate: Wed May 15 11:37:37 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8af3a078
dev-lisp/c2ffi: Clang-based FFI wrapper generator for Common Lisp
Closes: https://github.com/gentoo/gentoo/pull/11995
Closes: https://bugs.gentoo.org/673970
Signed-off-by: Harald Judt <h.judt <AT> gmx.at>
Signed-off-by: Michael Palimaka <kensington <AT> gentoo.org>
dev-lisp/c2ffi/c2ffi-8.0.0.9999.ebuild | 20 ++++++++++++++++++++
dev-lisp/c2ffi/metadata.xml | 15 +++++++++++++++
2 files changed, 35 insertions(+)
diff --git a/dev-lisp/c2ffi/c2ffi-8.0.0.9999.ebuild b/dev-lisp/c2ffi/c2ffi-8.0.0.9999.ebuild
new file mode 100644
index 00000000000..52bbf27c3bd
--- /dev/null
+++ b/dev-lisp/c2ffi/c2ffi-8.0.0.9999.ebuild
@@ -0,0 +1,20 @@
+# Copyright 2019 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+inherit cmake-utils git-r3
+
+DESCRIPTION="Clang-based FFI wrapper generator for Common Lisp"
+HOMEPAGE="https://github.com/rpav/c2ffi"
+EGIT_REPO_URI="https://github.com/rpav/c2ffi.git"
+EGIT_BRANCH="llvm-8.0.0"
+
+LICENSE="LGPL-2.1"
+SLOT="8"
+IUSE=""
+
+DEPEND="sys-devel/clang:8
+ sys-devel/llvm:8
+"
+RDEPEND="${DEPEND}"
diff --git a/dev-lisp/c2ffi/metadata.xml b/dev-lisp/c2ffi/metadata.xml
new file mode 100644
index 00000000000..d30f4079e72
--- /dev/null
+++ b/dev-lisp/c2ffi/metadata.xml
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+<maintainer type="person">
+ <email>h.judt@gmx.at</email>
+ <name>Harald Judt</name>
+</maintainer>
+<maintainer type="project">
+ <email>proxy-maint@gentoo.org</email>
+ <name>Proxy Maintainers</name>
+</maintainer>
+<upstream>
+ <remote-id type="github">rpav/c2ffi</remote-id>
+</upstream>
+</pkgmetadata>
next reply other threads:[~2019-05-15 11:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 11:37 Michael Palimaka [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-12-13 13:49 [gentoo-commits] repo/gentoo:master commit in: dev-lisp/c2ffi/ Joonas Niilola
2020-01-01 10:17 Andreas Sturmlechner
2020-12-10 7:31 Joonas Niilola
2020-12-10 7:31 Joonas Niilola
2020-12-10 7:31 Joonas Niilola
2021-07-06 12:34 Joonas Niilola
2022-07-18 21:37 Conrad Kostecki
2022-07-18 21:37 Conrad Kostecki
2022-08-17 16:18 Joonas Niilola
2022-08-17 16:18 Joonas Niilola
2022-08-17 16:18 Joonas Niilola
2022-10-12 23:32 Sam James
2022-10-12 23:32 Sam James
2022-10-12 23:32 Sam James
2023-06-09 5:51 Sam James
2023-06-09 5:51 Sam James
2023-10-17 5:27 Yixun Lan
2023-10-17 5:27 Yixun Lan
2024-04-15 6:32 Joonas Niilola
2024-04-15 6:32 Joonas Niilola
2024-09-27 5:57 Eli Schwartz
2024-09-27 5:57 Eli Schwartz
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=1557920257.8af3a0782b735703438a02928d1ec8126c2dfaa0.kensington@gentoo \
--to=kensington@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