BSD Ports

devel/rubygem-jira-ruby-gitlab 2.3.0 MidnightBSD

API for JIRA

System
MidnightBSD
Repository
mports
Maintainer
[email protected]
Last update
Commit
a632c268d2
License
mit
Categories
devel, rubygems

Description

This gem provides access to the Atlassian JIRA REST API.

In the other systems

SystemPortVersion
MidnightBSDdevel/rubygem-jira-ruby-gitlab2.3.0
FreeBSDdevel/rubygem-jira-ruby-gitlab3.2.0
DragonFlydevel/rubygem-jira-ruby-gitlab2.3.0
HardenedBSDdevel/rubygem-jira-ruby-gitlab3.2.0
GhostBSDdevel/rubygem-jira-ruby-gitlab3.2.0

Install

Binary package:

mport install jira-ruby-gitlab

From mports:

cd /usr/mports/devel/rubygem-jira-ruby-gitlab && make install clean

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

RUN_DEPENDS=	jira-ruby-gitlab>0:devel/rubygem-jira-ruby-gitlab

Dependencies

As this port's Makefile names them.

Build 4

Runtime 4

Build dependencies 4
Run dependencies 4

No port depends on this one.

Configuration

No options to configure.

USES
gem
Service scripts
none

Files

distinfo 1
FileSizeSHA256
rubygem/jira-ruby-2.3.0.gem67072abf26e6bff4a8ea40bae06f7df6276a5776905c63fb2070934823ca54f62eb62
Master sites 1
  • RG

Commit history 1

DateCommitCreditsLog message
a632c268d2 Lucas Holt devel/rubygem-jira-ruby-gitlab: install RUN_DEPENDS at build time
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]> Signed-off-by: Lucas Holt <[email protected]>