From: "Joe Kappus" <joe@wt.gd>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: dev-libs/libdbf/
Date: Tue, 24 Jan 2023 09:17:39 +0000 (UTC) [thread overview]
Message-ID: <1674551745.02384611f1762be27c0406bd5232d2af64bab965.joe@gentoo> (raw)
commit: 02384611f1762be27c0406bd5232d2af64bab965
Author: Joe Kappus <joe <AT> wt <DOT> gd>
AuthorDate: Tue Jan 24 09:15:45 2023 +0000
Commit: Joe Kappus <joe <AT> wt <DOT> gd>
CommitDate: Tue Jan 24 09:15:45 2023 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=02384611
dev-libs/libdbf: new package, add 0.0.1
Signed-off-by: Joe Kappus <joe <AT> wt.gd>
dev-libs/libdbf/Manifest | 1 +
dev-libs/libdbf/libdbf-0.0.1.ebuild | 42 +++++++++++++++++++++++++++++++++++++
dev-libs/libdbf/metadata.xml | 14 +++++++++++++
3 files changed, 57 insertions(+)
diff --git a/dev-libs/libdbf/Manifest b/dev-libs/libdbf/Manifest
new file mode 100644
index 000000000..914873a45
--- /dev/null
+++ b/dev-libs/libdbf/Manifest
@@ -0,0 +1 @@
+DIST libdbf-0.0.1.tgz 66443 BLAKE2B 543aff47c42d19dbe738fa50fe65dd6914a43695851395cf340f53718022e229896c6651f8a5cef8f0a46226efa91563d64ec072dbd1546997c729eca34f67dd SHA512 39df9e958582f224480bdf3b8afd9683427c090e252273004909af0443fddcc149b4dcfd3a09291c9b8786c096ce68cae3310dc692f112f102e51061a68b53f2
diff --git a/dev-libs/libdbf/libdbf-0.0.1.ebuild b/dev-libs/libdbf/libdbf-0.0.1.ebuild
new file mode 100644
index 000000000..e28716c30
--- /dev/null
+++ b/dev-libs/libdbf/libdbf-0.0.1.ebuild
@@ -0,0 +1,42 @@
+# Copyright 1999-2023 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Header: $
+
+EAPI=8
+
+inherit autotools
+
+MY_COMMIT="d86e1dfb1e70f61b9227817dbccd20955cd8a86a"
+
+DESCRIPTION="Library to read the content of dBASE III, IV, and 5.0 files"
+HOMEPAGE="https://github.com/rollinhand/libdbf"
+SRC_URI="https://github.com/rollinhand/libdbf/archive/${MY_COMMIT}.tar.gz -> ${P}.tgz"
+
+LICENSE="GPL-2"
+SLOT="0"
+KEYWORDS="~amd64 ~x86"
+IUSE="doc"
+
+RDEPEND=""
+DEPEND="${RDEPEND}
+ dev-perl/XML-Parser
+ doc? ( app-text/docbook-sgml-utils )
+ virtual/pkgconfig"
+
+S="${WORKDIR}/${PN}-${MY_COMMIT}"
+
+src_prepare() {
+ default
+ eautoreconf
+}
+
+src_configure() {
+ if use doc; then
+ export DOC_TO_MAN=docbook2man
+ fi
+ econf
+}
+
+src_install() {
+ emake DESTDIR="${D}" install || die "make install failed"
+}
diff --git a/dev-libs/libdbf/metadata.xml b/dev-libs/libdbf/metadata.xml
new file mode 100644
index 000000000..c77d59f2d
--- /dev/null
+++ b/dev-libs/libdbf/metadata.xml
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "https://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+<maintainer type="person">
+ <email>joe@wt.gd</email>
+ <name>joecool</name>
+</maintainer>
+<upstream>
+ <remote-id type="github">rollinhand/libdbf</remote-id>
+</upstream>
+<use>
+ <flag name="doc">Include documentation</flag>
+</use>
+</pkgmetadata>
next reply other threads:[~2023-01-24 9:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 9:17 Joe Kappus [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-24 16:12 [gentoo-commits] repo/proj/guru:dev commit in: dev-libs/libdbf/ Joe Kappus
2024-01-14 9:34 Joe Kappus
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=1674551745.02384611f1762be27c0406bd5232d2af64bab965.joe@gentoo \
--to=joe@wt.gd \
--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