| Port details on branch 2025Q4 |
- go-carbon Go implementation of carbon
- 0.12.0_31 databases
=0 0.12.0_31Version of this port present on the latest quarterly branch. - Maintainer: a.andersson.thn@gmail.com
 - Port Added: 2025-11-01 15:53:31
- Last Update: 2025-11-01 15:48:35
- Commit Hash: ae07b4c
- License: MIT
- WWW:
- https://github.com/lomik/go-carbon
- Description:
- go-carbon is a go implementation of the carbon component of the graphite
project. It has support for multiple cpu's and can achieve higher concurrency.
¦ ¦ ¦ ¦ 
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - USE_RC_SUBR (Service Scripts)
-
- Dependency lines:
-
- go-carbon>0:databases/go-carbon
- To install the port:
- cd /usr/ports/databases/go-carbon/ && make install clean
- To add the package, run one of these commands:
- pkg install databases/go-carbon
- pkg install go-carbon
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.- PKGNAME: go-carbon
- Flavors: there is no flavor information for this port.
- distinfo:
- TIMESTAMP = 1521477973
SHA256 (lomik-go-carbon-v0.12.0_GH0.tar.gz) = 2661492a9b0209977548ef86340f606e29630ab9d5d971bdf745d4b30495875c
SIZE (lomik-go-carbon-v0.12.0_GH0.tar.gz) = 3035132
Packages (timestamps in pop-ups are UTC):
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- go124 : lang/go124
- There are no ports dependent upon this port
Configuration Options:
- No options to configure
- Options name:
- databases_go-carbon
- USES:
- go
- FreshPorts was unable to extract/find any pkg message
- Master Sites:
|
Number of commits found: 1
| Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
| Commit | Credits | Log message |
0.12.0_31 01 Nov 2025 15:48:35
    |
Adam Weinberger (adamw)  |
various: Bump Go ports for 1.24.9
This is a direct commit to 2025Q4. It'll definitely bring things (esp.
PORTREVISION lines) out of sync with main, but trying to MFH the
associated bump commit would bring in a massive quantity of conflicts. |
Number of commits found: 1
|