# -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- vim:fenc=utf-8:ft=tcl:et:sw=4:ts=4:sts=4 PortSystem 1.0 PortGroup golang 1.0 go.setup github.com/zaquestion/lab 0.25.1 v revision 0 categories devel platforms darwin license public-domain maintainers {nixgeex.org:c.wrinn @cwrinn} openmaintainer description git-wrapper for GitLab specific functionality long_description \ Lab wraps Git or Hub, making it simple to clone, fork, and interact with \ repositories on GitLab, including seamless workflows for creating merge \ requests, issues and snippets. homepage https://zaquestion.github.io/lab checksums rmd160 bc2a30535ce385500f56eb2c2288acb5bc64ec24 \ sha256 f8cccdfbf1ca5a2c76f894321a961dfe0dc7a781d95baff5181eafd155707d79 \ size 180159 github.tarball_from archive # Allow Go to fetch deps at build time go.offline_build no build.cmd make build.pre_args-append \ VERSION=${github.tag_prefix}${version} build.args build notes " # Configuration lab needs your GitLab information in order to interact with to your GitLab instance. There are several ways to provide this information to lab: 1. Environment variables: LAB_CORE_HOST, LAB_CORE_USER, LAB_CORE_TOKEN 2. Environment variables: CI_PROJECT_URL, CI_REGISTRY_USER, CI_JOB_TOKEN * Note: these are meant for when lab is running within a GitLab CI pipeline 3. HCL config file: ./lab.hcl 4. HCL config file: ~/.config/lab.hcl These are checked in order. If no suitable config values are found, lab will prompt for your GitLab information and save it into ~/.config/lab.hcl. For example: ``` $ lab Enter default GitLab host (default: https://gitlab.com): Enter default GitLab user: zaq Enter default GitLab token: ``` Like hub, lab feels best when aliased as git. In your .bashrc or .bash_profile, put: alias git=lab " destroot { xinstall -m 0755 ${worksrcpath}/${name} ${destroot}${prefix}/bin/ }