From: "Craig Andrews" <candrews@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libfstrcmp/
Date: Wed, 25 Jul 2018 14:15:33 +0000 (UTC) [thread overview]
Message-ID: <1532528122.2c222f7234ddbd2a73917c06e2b6e44a939e9c8f.candrews@gentoo> (raw)
commit: 2c222f7234ddbd2a73917c06e2b6e44a939e9c8f
Author: Craig Andrews <candrews <AT> gentoo <DOT> org>
AuthorDate: Wed Jul 25 14:04:18 2018 +0000
Commit: Craig Andrews <candrews <AT> gentoo <DOT> org>
CommitDate: Wed Jul 25 14:15:22 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2c222f72
dev-libs/libfstrcmp: Make fuzzy comparisons of strings and byte arrays
Package-Manager: Portage-2.3.43, Repoman-2.3.10
dev-libs/libfstrcmp/Manifest | 1 +
dev-libs/libfstrcmp/libfstrcmp-0.7.ebuild | 15 +++++++++++++++
dev-libs/libfstrcmp/metadata.xml | 8 ++++++++
3 files changed, 24 insertions(+)
diff --git a/dev-libs/libfstrcmp/Manifest b/dev-libs/libfstrcmp/Manifest
new file mode 100644
index 00000000000..3863e80feee
--- /dev/null
+++ b/dev-libs/libfstrcmp/Manifest
@@ -0,0 +1 @@
+DIST libfstrcmp-0.7.tar.gz 394845 BLAKE2B a8b68fcb8613f0d30e5ff7b862b37408472162585ca71cdff328e3299ff50476fd265467bbd77b352b22bb88c590969044f74d91c5468475504568fd269fa69e SHA512 aaeb0227afd5ada5955cbe6a565254ff88d2028d677d199c00e03b7cb5de1f2c69b18e6e8b032e452350a8eda7081807b01765adbeb8476eaf803d9de6e5509c
diff --git a/dev-libs/libfstrcmp/libfstrcmp-0.7.ebuild b/dev-libs/libfstrcmp/libfstrcmp-0.7.ebuild
new file mode 100644
index 00000000000..c156bb325b5
--- /dev/null
+++ b/dev-libs/libfstrcmp/libfstrcmp-0.7.ebuild
@@ -0,0 +1,15 @@
+# Copyright 1999-2018 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+DESCRIPTION="Make fuzzy comparisons of strings and byte arrays"
+HOMEPAGE="http://fstrcmp.sourceforge.net/"
+
+LICENSE="GPL-3+"
+IUSE="test"
+SLOT="0"
+
+SRC_URI="http://fstrcmp.sourceforge.net/fstrcmp-0.7.D001.tar.gz -> ${P}.tar.gz"
+S="${WORKDIR}/fstrcmp-0.7.D001"
+KEYWORDS="~amd64 ~x86"
diff --git a/dev-libs/libfstrcmp/metadata.xml b/dev-libs/libfstrcmp/metadata.xml
new file mode 100644
index 00000000000..fbb8d54dbc4
--- /dev/null
+++ b/dev-libs/libfstrcmp/metadata.xml
@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+ <maintainer type="person">
+ <email>candrews@gentoo.org</email>
+ <name>Craig Andrews</name>
+ </maintainer>
+</pkgmetadata>
next reply other threads:[~2018-07-25 14:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 14:15 Craig Andrews [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-25 14:35 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libfstrcmp/ Craig Andrews
2018-07-25 20:12 Craig Andrews
2018-11-27 21:39 Craig Andrews
2018-11-28 2:07 Thomas Deutschmann
2018-12-13 15:46 Mikle Kolyada
2020-05-28 14:01 Craig Andrews
2020-07-14 22:39 Sam James
2021-03-29 14:50 Sam James
2021-05-16 18:53 Sam James
2021-07-26 1:39 Sam James
2022-06-20 2:21 Sam James
2022-08-27 11:45 Yixun Lan
2024-08-29 19:03 Andreas Sturmlechner
2024-08-29 19:42 Sam James
2024-08-29 19:43 Sam James
2024-08-29 19:43 Sam James
2024-08-30 13:11 Andreas Sturmlechner
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=1532528122.2c222f7234ddbd2a73917c06e2b6e44a939e9c8f.candrews@gentoo \
--to=candrews@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