| Port details |
- flare Flare - distributed and persistent key-value storage
- 1.0.9_5 databases
 =0      1.0.9_5Version of this port present on the latest quarterly branch.  BROKEN: Does not build
 DEPRECATED: Not staged. See http://lists.freebsd.org/pipermail/freebsd-ports-announce/2014-May/000080.html
 This port expired on: 2014-08-31
 IGNORE: is marked as broken: Does not build
- There is no maintainer for this port.
- Any concerns regarding this port should be directed to the FreeBSD Ports mailing list via ports@FreeBSD.org
- Port Added: 2010-05-30 04:42:51
- Last Update: 2014-09-01 12:53:55
- SVN Revision: 366869
- License: GPLv2
- WWW:
- http://labs.gree.jp/Top/OpenSource/Flare-en.html
- Description:
- Flare is distributed, and persistent key-value storage compatible
w/ memcached, and has more features(as follows):
* persistent storage (you can use flare as persistent memcached)
* pluggable storage (currently only Tokyo Cabinet is available, though:)
* data replication (synchronous or asynchronous)
* data partitioning (automatically partitioned according to # of master
servers (clients do not have to care about it))
* dynamic reconstruction, and partitioning (you can dynamically (I mean,
without any service interruption) add slave servers and partition
master servers)
* node monitoring and failover (if any server is down, the server is
automatically isolated from active servers and another slave server
is promoted to master server)
* request proxy (you can always get same result regardless of servers
you connect to. so you can think flare servers as one big key-value
storage)
* over 256 bytes keys, and over 1M bytes values are available
WWW: http://labs.gree.jp/Top/OpenSource/Flare-en.html
 cgit ¦ GitHub ¦ GitHub ¦ GitLab ¦ 
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - There is no configure plist information for this port.
- Dependency lines:
-
- flare-db>0:databases/flare
- No installation instructions:
- This port has been deleted.
- PKGNAME: flare-db
- Flavors: there is no flavor information for this port.
- distinfo:
- There is no distinfo for this port.
No package information for this port in our database- Sometimes this happens. Not all ports have packages. Perhaps there is a build error. Check the fallout link:
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Library dependencies:
-
- libboost_program_options.so : devel/boost-libs
- libtokyocabinet.so : databases/tokyocabinet
- There are no ports dependent upon this port
Configuration Options:- No options to configure
- Options name:
- N/A
- FreshPorts was unable to extract/find any pkg message
- Master Sites:
|
| Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
| Commit | Credits | Log message |
|---|
1.0.9_5
01 Sep 2014 12:53:55
  |
bapt |
Remove non staged ports without pending PR from databases |
1.0.9_5
28 Feb 2014 19:45:27
|
antoine |
Mark more ports BROKEN
Error logs are available in the pkg-fallout archives
Reported by: pkg-fallout since at least january 2014 |
1.0.9_5
07 Feb 2014 11:44:09
|
bapt |
Chase boost and icu bump
While here convert some LIB_DEPENDS |
1.0.9_4
20 Sep 2013 16:13:49
|
bapt |
Add NO_STAGE all over the place in preparation for the staging support (cat:
databases) |
1.0.9_4
16 Sep 2013 13:11:43
|
bapt |
Rename the package to flare-db to avoid confusion with games/flare
While here modernize and cleanup |
14 Aug 2013 22:35:54
 
|
ak |
- Remove MAKE_JOBS_SAFE variable
Approved by: portmgr (bdrewery) |
1.0.9_4
28 Mar 2013 16:29:01
|
eadler |
Style: tab -> space.
Most contributors copy an existing port when writing their own so reduce the
number of bad examples in the tree. |
1.0.9_4
31 Jan 2013 13:38:43
|
bapt |
Chase boost update |
1.0.9_3
15 Aug 2012 19:26:14
|
tabthorpe |
- Reassign nork@ ports to the heap
- Thank you for your years of service, we hope to see you back
Approved by: portmgr |
1.0.9_3
25 Jul 2012 06:32:08
|
cs |
Fix typos in COMMENT |
1.0.9_3
14 Jan 2012 08:57:23
|
dougb |
In the rc.d scripts, change assignments to rcvar to use the
literal name_enable wherever possible, and ${name}_enable
when it's not, to prepare for the demise of set_rcvar().
In cases where I had to hand-edit unusual instances also
modify formatting slightly to be more uniform (and in
some cases, correct). This includes adding some $FreeBSD$
tags, and most importantly moving rcvar= to right after
name= so it's clear that one is derived from the other. |
1.0.9_3
23 Sep 2011 22:26:39
|
amdmi3 |
- Add LDFLAGS to CONFIGURE_ENV and MAKE_ENV (as it was done with LDFLAGS)
- Fix all ports that add {CPP,LD}FLAGS to *_ENV to modify flags instead
PR: 157936
Submitted by: myself
Exp-runs by: pav
Approved by: pav |
1.0.9_3
20 Mar 2011 12:54:45
|
miwi |
- Get Rid MD5 support |
1.0.9_3
01 Jul 2010 04:04:02
|
linimon |
Mark as broken on sparc64: does not compile.
Hat: portmgr
Feature safe: yes |
1.0.9_3
31 May 2010 16:43:38
|
nork |
Cleanup rc script, and bump PORTREVISION.
Submitted by: dougb |
1.0.9_2
30 May 2010 15:05:18
|
nork |
o Fix my HAVE_KQUEUE support bugs.
o Add support `service flare[id] reload'.
o Sleep until flarei daemon starting.
To disable flarei_sleepwait="0" to /etc/rc.conf. |
1.0.9_1
30 May 2010 06:40:24
|
nork |
Temporary disable HAVE_KQUEUE by performance and stability issue. |
1.0.9
30 May 2010 04:41:50
|
nork |
Add flare 1.0.9, is distributed, and persistent key-value storage
compatible / memcached, and has more features(as follows):
* persistent storage (you can use flare as persistent memcached)
* pluggable storage (currently only Tokyo Cabinet is available, though:)
* data replication (synchronous or asynchronous)
* data partitioning (automatically partitioned according to # of master
servers (clients do not have to care about it))
* dynamic reconstruction, and partitioning (you can dynamically (I mean,
without any service interruption) add slave servers and partition
master servers)
* node monitoring and failover (if any server is down, the server is
automatically isolated from active servers and another slave server
is promoted to master server)
* request proxy (you can always get same result regardless of servers
you connect to. so you can think flare servers as one big key-value
storage)
* over 256 bytes keys, and over 1M bytes values are available
WWW: http://labs.gree.jp/Top/OpenSource/Flare-en.html |
As an Amazon Associate I earn from qualifying purchases.