You are not logged in.
- Topics: Active | Unanswered
#1 2016-11-11 02:53:53
- adamlau
- Member
- Registered: 2009-01-30
- Posts: 418
Git Package Naming Convention?
With r (revision) or without r? With g (commit) or without g? . or +?
libxml2 [extra] = 2.9.4+12+ge905f08 = without r | with g | with +
libfdk-aac [community-testing] = 0.1.4.r88.5fd7e65 = with r | without g | with .
Many other examples of this inconsistency exist within the official repos. AUR packages are all over the place as well. What is the official and/or recommended naming convention?
Last edited by adamlau (2016-11-11 02:57:43)
Arch Linux + sway
Debian Testing + GNOME/sway
NetBSD 64-bit + Xfce
Offline
#2 2016-11-11 03:23:32
- eschwartz
- Fellow
- Registered: 2014-08-08
- Posts: 4,097
Re: Git Package Naming Convention?
With r, with g, with "." rather than "+"
AUR packages have the "official" VCS package guidelines in the Wiki, which give the recommended pkgver function.
I have no idea why some repo packages use pluses instead.
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline
#3 2016-11-11 04:27:53
- jasonwryan
- Anarchist
- From: .nz
- Registered: 2009-05-09
- Posts: 30,424
- Website
Re: Git Package Naming Convention?
Moving to Creating & Modifying Packages...
Offline
#4 2016-11-12 14:01:20
- Lone_Wolf
- Member
- From: Netherlands, Europe
- Registered: 2005-10-04
- Posts: 11,914
Re: Git Package Naming Convention?
Keep in mind both libxml2 or libfdk-aac are stable, non-VCS packages .
They just download a specific commit from a git-repo instead of a tarball.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline