Package Details: libarchive-git 3.6.2.r19.gaa091636-1

Git Clone URL: https://aur.archlinux.org/libarchive-git.git (read-only, click to copy)
Package Base: libarchive-git
Description: Multi-format archive and compression library
Upstream URL: https://libarchive.org/
Licenses: custom, BSD
Conflicts: libarchive
Provides: libarchive
Submitter: J5lx
Maintainer: Chocobo1
Last Packager: Chocobo1
Votes: 0
Popularity: 0.000000
First Submitted: 2016-12-26 14:38 (UTC)
Last Updated: 2023-04-11 07:22 (UTC)

Required by (499)

Sources (1)

Latest Comments

J5lx commented on 2017-01-12 23:15 (UTC)

I got that git line from /usr/share/pacman/PKGBUILD-vcs.proto. That file is part of the official pacman distribution and I suppose that the authors put some thought into it. If you think the line could be improved, you should first contact the pacman devs about it (I guess FS or ML would be good options). Depending on what they think about it, I might change this package as well. As for my own two cents: I guess --always wouldn't exactly hurt here, but I'm pretty sure allowing lightweight tags in pkgver via --tags would be a bad idea. From git-tag(1): "Annotated tags are meant for release while lightweight tags are meant for private or temporary object labels." I have never seen any project that didn't adhere to that "rule", and putting private or temporary stuff of any kind into packages that other people might install simply doesn't sound right to me.

MRWITEK commented on 2017-01-12 22:08 (UTC)

I think, you should replace this line in pkgver(): printf "%s" "$(git describe --long | sed 's/\([^-]*-\)g/r\1/;s/-/./g')" with git describe --long --tags --always | sed 's/-/.r/;s/-g/./;s/-/./g' Or, at least, add --tags --always options to the git command.