Package Details: go-git 1:go1.15beta1.r138.gba9e1088997-1

Git Clone URL: (read-only, click to copy)
Package Base: go-git
Description: Core compiler tools for the Go programming language
Upstream URL:
Keywords: git go golang
Licenses: BSD
Conflicts: go
Provides: go
Submitter: fzerorubigd
Maintainer: obedmr
Last Packager: obedmr
Votes: 8
Popularity: 0.000004
First Submitted: 2014-12-18 12:40 (UTC)
Last Updated: 2020-08-07 17:52 (UTC)

Dependencies (2)

Required by (3303)

Sources (1)

Latest Comments

1 2 3 Next › Last »

obedmr commented on 2020-08-07 16:57 (UTC)

Hey @katt, thanks for your comment, I'm fixing it right away.

katt commented on 2020-08-07 16:46 (UTC)

Seriously? Someone pointed out in 2018 that this is lacking a pkgver() function and there still isn't one and it has only gotten worse?

What on earth are you even getting this "2020.8.7" from, are you just putting whatever the date is when you pushed the package as the pkgver? Why?!

acomagu commented on 2020-01-01 14:52 (UTC)

Why isn't provides=(go) in the top level? It prevents to recognize statically. e.g. go-tools-git AUR page don't show the go-git as go alternative.

obedmr commented on 2019-01-18 15:44 (UTC)

@SamWhited thanks for your comment, indeed, you're totally correct, I havent had the chance to update the go-git package to the latest commit in master. I update it to current's latest commit, will update it later to dont require the commit hash.

SamWhited commented on 2018-12-16 21:42 (UTC)

Hi; most -git packages build the latest version at the time the package is built and set the version using the pkgver function to something based on the latest tag, number of commits since the tag, and current hash.

Is there a reason this package does not do that and is pinned to a specific version (which will generally be out of date for a -git package)?

obedmr commented on 2018-10-02 15:47 (UTC)

Thanks @orax for the out-of-date flag, I'm updating it right now. New version is comming soon.

elgs commented on 2018-09-01 20:40 (UTC) (edited on 2018-09-01 20:41 (UTC) by elgs)

@obedmr thanks for the explanation. I guess I should switch to go-git. The official one's maintainers seem to show no interest in catching up with the latest release. Packages being up to date is the main reason I love Arch.

obedmr commented on 2018-08-31 15:08 (UTC)

@elgs that's a good question. This is AUR which stands for Archlinux User Repository, all packages here are just not official, the ones at are the one that are hosted in the official Archlinux repos.

This particular case of go-git exists for those who want the latest of latest in golang and not necesary the most stable. It's build from the source code on latest commit and not necesary an offcial release of go.

For stable releases, official Archlinux-provided packages are the right choice instead of AUR ones.

elgs commented on 2018-08-31 06:30 (UTC) (edited on 2018-08-31 06:31 (UTC) by elgs)

I suddenly realized go and go-git are two different packages. I used to install go with sudo pacman -S go, and it seems the go package is outdated. I'm wondering whether I should completely uninstall the go package and switch to go-git?

obedmr commented on 2018-08-30 15:08 (UTC)

Thanks @abonafide for your contribution, I just updated it.