BSD Ports

textproc/rubygem-elasticsearch-gitlab 7.17.11 MidnightBSD

Ruby integrations for Elasticsearch

System
MidnightBSD
Repository
mports
Maintainer
[email protected]
Last update
Commit
7dd6876e2b
License
Apache-2.0
Categories
textproc, rubygems

Description

Ruby integrations for Elasticsearch that feature:

* a client for connecting to an Elasticsearch cluster * a Ruby API for the Elasticsearch's REST API * various extensions and utilities

In the other systems

SystemPortVersion
MidnightBSDtextproc/rubygem-elasticsearch-gitlab7.17.11
FreeBSDtextproc/rubygem-elasticsearch-gitlab7.17.11
DragonFlytextproc/rubygem-elasticsearch-gitlab7.17.11

Install

Binary package:

mport install elasticsearch-gitlab

From mports:

cd /usr/mports/textproc/rubygem-elasticsearch-gitlab && make install clean

To depend on this port in another port's Makefile:

RUN_DEPENDS=	elasticsearch-gitlab>0:textproc/rubygem-elasticsearch-gitlab

Dependencies

As this port's Makefile names them.

Build 2

Runtime 2

Build dependencies 2
Run dependencies 2

Configuration

No options to configure.

USES
gem
Service scripts
none

Files

distinfo 1
FileSizeSHA256
rubygem/elasticsearch-7.17.11.gem15360ed080f085d939f21d07f424ebcea95326e4bdb5f770a8f33aac699374f2ffc86
Master sites 1
  • RG

Commit history 1

DateCommitCreditsLog message
7dd6876e2b Lucas Holt textproc/rubygem-elasticsearch-gitlab: fix the dependency version upper bound and install RUN_DEPENDS at build time
mport.query does not match a package when the lower bound of a range equals the upper bound's base version and the upper bound carries a _N suffix: "version>=1.1.1<1.1.1_99" reports not found for an installed 1.1.1, while "version>=1.1.1<1.1.1.99" matches, including packages carrying a PORTREVISION. Spell the bound with .99 so the dependency resolves. The gemdeps QA check runs ${LOCALBASE}/bin/gem list, so the runtime gems have to be installed before fake-qa. The build cluster installs BUILD_DEPENDS but not RUN_DEPENDS, so the check reported dependencies as unsatisfied even though they had built successfully in the same run. This matches the convention already used by most rubygem ports. AI-Assisted-by: Claude Opus 5 (1M context) <[email protected]> …