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!
===> The following configuration options are available for pgroonga-4.1.0:
MECAB=off: Use MeCab as a tokenizer
===> Use 'make config' to modify these settings
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
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, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
Mark BROKEN
src/pgroonga.c:77:6: error: redefinition of 'PGrnGroongaInitialized' with a
different type: 'bool' vs 'bool' (aka 'char')
bool PGrnGroongaInitialized = false;
^
src/pgroonga.h:94:13: note: previous declaration is here
extern bool PGrnGroongaInitialized;
^
src/pgroonga.c:7094:1: error: conflicting types for 'PGrnIndexIsPGroonga'
PGrnIndexIsPGroonga(Relation index)
^
src/pgroonga.h:97:6: note: previous declaration is here
bool PGrnIndexIsPGroonga(Relation index);
^
Reported by: pkg-fallout
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
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)
[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/