Historical bug tracker for the Pacman package manager.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
FS#43711 - pkgver() function fails to implement defaults
Attached to Project:
Pacman
Opened by James (thx1138) - Thursday, 05 February 2015, 20:12 GMT
Last edited by Allan McRae (Allan) - Friday, 06 February 2015, 00:00 GMT
Opened by James (thx1138) - Thursday, 05 February 2015, 20:12 GMT
Last edited by Allan McRae (Allan) - Friday, 06 February 2015, 00:00 GMT
|
Detailspacman 4.2.0-6
As described in "VCS package guidelines", https://wiki.archlinux.org/index.php/VCS_package_guidelines there are very specific recommendations for automatic versioning, covering Git, Subversion, Mercurial, Bazaar, and a fallback, based upon date. To establish a uniform versioning scheme for VCS packages, these recommendations should be incorporated into pacman, to be applied automatically, as defaults, based upon the VCS type. People could still over-ride these defaults with an explicit pkgver() function in the PKGBUILD, but otherwise, there is no reason to engage in "busywork", copying these pkgver() recommendations from the "VCS package guidelines". |
This task depends upon
Closed by Allan McRae (Allan)
Friday, 06 February 2015, 00:00 GMT
Reason for closing: Won't implement
Friday, 06 February 2015, 00:00 GMT
Reason for closing: Won't implement
Comment by Allan McRae (Allan) -
Friday, 06 February 2015, 00:00 GMT
No - these are Arch Linux recommendations. Not makepkg ones.