On 09/06, notify@aur.archlinux.org wrote:
pzl [1] filed a deletion request for tint2-git [2]:
This package should ideally be called tint2-beta if it's tied to particular release versions (including candidates, beta, any tag, including 0.12-rc5 as it is currently). This package should be renamed to beta (delete and recreate, whatever). tint2-git can then exist that tracks the master branch.
See the version-control package guidelines: https://wiki.archlinux.org/index.php/VCS_package_guidelines
The first one:
Suffix pkgname with ... -git ... unless the package fetches a specific release.
the last one:
Because the sources are not static, skip the checksum in md5sums by adding 'SKIP'
Black_Codec, could you upload the current tint2-git package as tint2-beta and send a merge request to merge the current -git package into -beta, or make the -git package a proper -git PKGBUILD? -- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias/