[Slackbuilds-users] development/gitlab-cli at SBo

Diniz Bortolotto diniz.bortolotto at gmail.com
Sun Jun 21 19:02:49 UTC 2026


Hi Chris and all,

I am writing to let you know that the gitlab-cli SlackBuild has been taken
over by Andrew Clemons.
I apologize for any delays or oversight on my part regarding this update.

Best regards,
Diniz Bortolotto



Em sex., 12 de jun. de 2026 às 07:40, Christoph Willing <
chris.willing at linux.com> escreveu:

> Hi Diniz,
>
> I figured out how to build it from source code which I prefer and also is
> more on the spirit of SlackBuilds.org. Would you be interested in
> converting your SlackBuild to use the source code instead of precompiled
> binary? I'm happy to give it to you to maintain.
>
> I've attached a tarball of the new version - just change the maintainer
> name and submit to SBo.
>
> It's a bit different to normal SlackBuilds because we need to stop it
> downloading .go files while building (SBo generally does not allow network
> access when testing submissions). Therefore the maintainer must run the
> SlackBuild before submitting. This will create a "vendor" tarball of the
> .go files that are needed and stop running. When the vendor tarball is
> made, it should be uploaded to slackbuildsdirectlinks at sourceforge. This
> is a common repo for files needed for various Slackbuilds. If the
> maintainer now runs the SlackBuild again, the required .go files are
> unpacked from the vendor tarball - no need for network access and the build
> now runs to completion. This is also how normal user will build - they have
> access to both source and vendor tarballs (listed in .info file), so can
> build without further network access.
>
> To upload to slackbuildsdirectlinks, you will need a sourceforge account.
> When you have that, email Willy and ask for access to
> slackbuildsdirectlinks.
>
> In this case, I uploaded the vendor tarball with:
>     rsync -av gitlab-cli-1.102.0-vendor.tar.xz
> cwilling at web.sourceforge.net:/home/frs/project/slackbuildsdirectlinks/gitlab-cli/
> All future vendor tarballs could go to the same location.
>
> Please ask any questions about this method - I am keen to have a
> build-from-source version at SBo.
>
> chris
>
>
> On 11/6/26 22:46, Diniz Bortolotto wrote:
>
> Hi Chris,
>
> Sorry for the delay in my response; the last few months have been quite
> busy.
>
> I'm glad to hear that the SlackBuild is being used.
> I will work on updating it to the latest version this weekend.
>
> Best regards,
> Diniz Bortolotto
>
>
>
> Em ter., 9 de jun. de 2026 às 09:26, Christoph Willing <
> chris.willing at linux.com> escreveu:
>
>> Hi Diniz,
>>
>> I see that you are listed as the maintainer for gitlab-cli at
>> SlackBuilds.org.
>>
>> The version in the SlackBuild is 1.51.0, published about 18 months ago.
>> The latest version at the gitlab repo is 1.102.0 and I wonder if you
>> would consider updating the SlackBuild for the new version?
>>
>> I notice that you haven't made any contributions at SBo since December
>> 2024. If you no longer wish to maintain gitlab-cli, I would be happy to
>> take over maintainership of this SlackBuild.
>>
>> What do you think?
>>
>> chris
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20260621/dfc30173/attachment.htm>


More information about the SlackBuilds-users mailing list