Package Details: lab 0.25.1-1

Git Clone URL: (read-only, click to copy)
Package Base: lab
Description: A hub-like tool for GitLab
Upstream URL:
Licenses: custom:CC0
Submitter: simon04
Maintainer: alerque (artafinde)
Last Packager: alerque
Votes: 6
Popularity: 0.000000
First Submitted: 2018-01-26 11:37 (UTC)
Last Updated: 2024-03-27 23:59 (UTC)

Dependencies (3)

Required by (0)

Sources (1)

Latest Comments

alerque commented on 2021-01-25 04:44 (UTC)

I have switched to using gitlab-glab. While this is a great tool I prefer the separate command approach of glab over the Git wrapper approach lab took. Since I'm no longer and active user I will probably recuse myself from maintaining all of the lab, lab-bin, and lab-git packages. I'll stay on a little longer to make sure there are timely updates, but if anyone else is interested in actively maintaining these be sure to let myself or @simon04 know. Since I'll no longer be motivated to keep it up to date I'll eventually drop the prebuilt package from my user reposiory as well.

alerque commented on 2020-09-25 13:12 (UTC)

Thanks @bionade24. Just for general information, it's also available in my user repository.

bionade24 commented on 2020-09-23 13:00 (UTC)

This package is built by my CD and available in this repo:
CI status:

alerque commented on 2020-05-26 23:27 (UTC)

Thanks for the catch @aperez. I'm unconvinced however that the fix will actually work though. I just did some testing in bash and that inner single quote doesn't actually help — given that the testing scenario is another bash function. The outer double quotes succeed in grouping the contents, but unless you do something fancy like array expansion other arguments still get split, albeit with a leading single quote on the first arg and a trailing single quote on the last arg. I don't know how Go itself handles parsing arguments here. Does it actually handle the single quotes here? Or would it handle if we passed it escaped double quotes instead? Note that this is the syntax recommended in the new Arch packaging guidelines for Go packages, so it's worth figuring out what actually works.

aperez commented on 2020-05-26 22:14 (UTC)

The build command is missing quoting on $LDFLAGS, which can easily result in failure when makepkg.conf defines it with a value that includes spaces. Could you please apply the following fix?

diff --git a/PKGBUILD b/PKGBUILD
index c8ad3bc..1490862 100644
@@ -29,7 +29,7 @@ build () {
         -buildmode=pie \
         -mod=readonly \
         -modcacherw \
-        -ldflags "-extldflags ${LDFLAGS} -X main.version=$pkgver" \
+        -ldflags "-extldflags '${LDFLAGS}' -X main.version=$pkgver" \
     ./lab completion bash > completion.bash
     ./lab completion zsh > completion.zsh


simon04 commented on 2019-12-31 16:20 (UTC)

@jdorel: Thanks for the pointer. Done in 0.17.2-2 and 0.17.2-3.

jdorel commented on 2019-12-31 16:02 (UTC)

Would you consider adding the ZSH completions in the PKGBUILD ?

alerque commented on 2018-07-20 09:06 (UTC) (edited on 2018-07-20 09:07 (UTC) by alerque)

The *-2 version of this package has the same upstream version as before (0.12.0) but it will now build from source on the target system. If you prefer to download and install the binary as build upstream you can use the lab-bin package which contains the PKGBUILD as it was in the *-1 package version. Also note there is a lab-git package available if you prefer to build from the master branch HEAD instead of the last tagged release.