9 Commits

Author SHA1 Message Date
Muhammad Moinur Rahman
b90d633b31 databases/pgroonga: Update version 2.1.7=>2.1.8
Relnotes:	https://pgroonga.github.io/news/
2019-01-13 09:18:52 +00:00
Muhammad Moinur Rahman
2b0c5b653a databases/pgroonga: Updare version 2.1.6=>2.1.7
Relnotes:https://pgroonga.github.io/news/
2018-12-31 17:35:50 +00:00
Muhammad Moinur Rahman
6a575ea721 databases/pgroonga: Update version 2.0.9=>2.1.6
- Pet portlint

Relnotes:https://pgroonga.github.io/news/#version-2-1-6
2018-12-19 08:30:04 +00:00
Gerald Pfeifer
a9f015d155 Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.

This includes ports
 - with USE_GCC=yes or USE_GCC=any,
 - with USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and
 - with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
   c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.

PR:		231590
2018-12-12 01:35:33 +00:00
Muhammad Moinur Rahman
ebc572646b databases/pgroonga: Update version 2.0.5=>2.0.9
Relnotes:	https://pgroonga.github.io/news/
2018-07-23 20:51:16 +00:00
Mark Linimon
078a5d7419 Workaround the following problem on aarch64 by setting LLD_UNSAFE=yes:
cc: error: invalid linker name in argument '-fuse-ld=bfd'

Neither emaste nor I can figure out exactly where the offending stanza is
coming in.  It will take someone with more knowledge of gmake debug flags,
and possibly the src build infrastructure, to figure it out.

While here, pet portlint.

Approved by:	portmgr (tier-2 blanket)
2018-06-24 00:54:27 +00:00
Muhammad Moinur Rahman
77696d9670 databases/pgroonga: Update version 2.0.2=>2.0.5
Relnotes:	https://pgroonga.github.io/news/
2018-04-22 22:39:09 +00:00
Muhammad Moinur Rahman
6264f6fcff databases/pgroonga: Update version 2.0.1=>2.0.2
Relnotes:	https://pgroonga.github.io/news/#version-2-0-2
2018-01-08 10:41:34 +00:00
Muhammad Moinur Rahman
515edc3eb1 [NEW] databases/pgroonga: Open-source fulltext search engine for PostGRESQL
PGroonga is a PostgreSQL extension. PGroonga provides a new index access
method that uses Groonga.

Groonga is an embeddable super fast full text search engine. It can be
embedded into MySQL. Mroonga is a storage engine that is based on Groonga.
Groonga can also work as standalone search engine.

PostgreSQL supports full text search against languages that use only
alphabet and digit. It means that PostgreSQL doesn't support full text
search against Japanese, Chinese and so on. You can use super fast full
text search feature against all languages by installing PGroonga into your
PostgreSQL!

WWW: https://pgroonga.github.io/
2017-09-19 19:48:30 +00:00