From: "Justin Lecher" <jlec@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sci:master commit in: sci-misc/hfst/
Date: Mon, 8 Jun 2015 12:19:53 +0000 (UTC) [thread overview]
Message-ID: <1433763680.5ff6a7a80f78892c925e40d3aa6f0a01956a0678.jlec@gentoo> (raw)
commit: 5ff6a7a80f78892c925e40d3aa6f0a01956a0678
Author: Justin Lecher <jlec <AT> gentoo <DOT> org>
AuthorDate: Mon Jun 8 11:41:20 2015 +0000
Commit: Justin Lecher <jlec <AT> gentoo <DOT> org>
CommitDate: Mon Jun 8 11:41:20 2015 +0000
URL: https://gitweb.gentoo.org/proj/sci.git/commit/?id=5ff6a7a8
sci-misc/hfst: Updating remote-id in metadata.xml
Package-Manager: portage-2.2.20
sci-misc/hfst/ChangeLog | 6 ++++--
sci-misc/hfst/metadata.xml | 19 +++++++++++--------
2 files changed, 15 insertions(+), 10 deletions(-)
diff --git a/sci-misc/hfst/ChangeLog b/sci-misc/hfst/ChangeLog
index 550fcb0..7ef0a3c 100644
--- a/sci-misc/hfst/ChangeLog
+++ b/sci-misc/hfst/ChangeLog
@@ -1,7 +1,10 @@
# ChangeLog for sci-misc/hfst
-# Copyright 1999-2013 Gentoo Foundation; Distributed under the GPL v2
+# Copyright 1999-2015 Gentoo Foundation; Distributed under the GPL v2
# $Header: $
+ 08 Jun 2015; Justin Lecher <jlec@gentoo.org> metadata.xml:
+ sci-misc/hfst: Updating remote-id in metadata.xml
+
03 Mar 2013; Justin Lecher <jlec@gentoo.org> hfst-3.0.2.ebuild,
hfst-3.3.12.ebuild, metadata.xml:
Add ~amd64 or ~x86 keywords for revdeps
@@ -28,4 +31,3 @@
17 Nov 2009; <flammie@gentoo.org> +hfst-2.2.ebuild, +metadata.xml:
Initial ebuild for HFST
-
diff --git a/sci-misc/hfst/metadata.xml b/sci-misc/hfst/metadata.xml
index 1e60332..4be3eac 100644
--- a/sci-misc/hfst/metadata.xml
+++ b/sci-misc/hfst/metadata.xml
@@ -1,28 +1,31 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
- <longdescription lang="en">
+ <longdescription lang="en">
Open Source API for FSTs, a set of command line tools, and clones of
traditional FST-based linguistic morphology tools.
</longdescription>
- <use>
- <flag name="openfst">
+ <use>
+ <flag name="openfst">
Add optional support for openfst backend library
(<pkg>sci-misc/openfst</pkg>)
</flag>
- <flag name="foma">
+ <flag name="foma">
Add optional support for foma backend library
(<pkg>sci-misc/foma</pkg>)</flag>
- <flag name="sfst">
+ <flag name="sfst">
Add optional support for sfst backend library
(<pkg>sci-misc/sfst</pkg>)
</flag>
- <flag name="glib">
+ <flag name="glib">
Parse UTF-8 and collate unicode using glib instead of
homebrewn methods
</flag>
- <flag name="xml">
+ <flag name="xml">
Include parsers for grammars and formats that require XML support
</flag>
- </use>
+ </use>
+ <upstream>
+ <remote-id type="sourceforge">hfst</remote-id>
+ </upstream>
</pkgmetadata>
next reply other threads:[~2015-06-08 12:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 12:19 Justin Lecher [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-27 18:40 [gentoo-commits] proj/sci:master commit in: sci-misc/hfst/ Aisha Tammy
2017-01-29 11:59 Justin Lecher
2012-07-31 21:34 Flammie Pirinen
2011-10-25 17:16 Justin Lecher
2011-06-24 17:09 Justin Lecher
2011-06-24 17:09 Justin Lecher
2011-05-09 18:28 Flammie Pirinen
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=1433763680.5ff6a7a80f78892c925e40d3aa6f0a01956a0678.jlec@gentoo \
--to=jlec@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