labstack / labstack/armor

Create Packages for Linux Distributions

Open
#48 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
1.7k
Forks
64
PR merge metrics
No merged PRs in 30d

Description

According to Repology, packages only exist for Homebrew, Linuxbrew, and Scoop -- and one of those is outdated. The BlackArch package there is for an unrelated tool.

Can the developers please contribute some packages, at least for one or two ports-like systems like Arch and Alpine, which would greatly assist others in the creation of other more-involved package types?

I haven't used armor yet, so am not familiar with -- for example -- what configuration directories and files it expects to be present. But here is a jump start for an Arch PKGBUILD:

pkgname=armor
pkgver=0.4.13
pkgrel=1
pkgdesc="Uncomplicated, modern HTTP server"
arch=('i686' 'x86_64')
url="https://github.com/labstack/armor"
license=('MIT')
makedepends=(go)
source=(${pkgname}-${pkgver}.tar.gz::${url}/archive/v${pkgver}.tar.gz)
sha256sums=('1e80b70c2fa245800594f3ef7b6bb14d2af4fda2a8622d3c8a0a28f9ef6c4629')

build() {
  cd ${srcdir}/${pkgname}-${pkgver}
  go build -o bin/armor cmd/armor/main.go
}

package() {
  cd ${srcdir}/${pkgname}-${pkgver}
  install -D -m755 bin/armor ${pkgdir}/usr/bin/armor
}

This at least works for the basic no-config test case.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the provided Arch PKGBUILD and the Go entry point cmd/armor/main.go; verify how the basic no-config case is built and run. Done means contributing a working package for at least one or two Linux distribution or ports-like systems, with the expected configuration paths accounted for.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.