Arch Linux User Repository

"git clone --bare" is part of the patch function. It's not used in this manner (the template simply contained it).

It's used to create a patch from a branch or commit in a foreign repository. This is much easier than managing patch-files for each package variant.

See https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=kopano-core-git#n266

Marti

Well, the missing hash is not a good reason to delete a whole package, right? Of course I can add that hashes. If that's your request/contribution here.

From my developers experience the last commit rarely is a good point to build anything productive from. So what most persons want to build, will be the last release. And the last tag is marking latest release.

Z-Push does not contain any branch named "latest". So there is nothing which will confuse anybody here. Indeed the appendix "-git" has been added by accident from my publishing script. But is this making any difference for you?

Maybe you are able to explain how and where I could implement a pkgbuild which always builds the last tag?

So far I could find, my only choices are writing a pkgbuild for the last commit or maintain a static release version.

My templates are located here https://github.com/pietmacom/kopano-pkgbuilds

That templates, the custom variables and functions make it a lot easier, or even possible, to maintain that many packages and versatile requirements.

marti

You're skippind hash check on files like z-push.ini and all except one of your VCS pkgbuilds don't a pkgver= calculated, like this one pkgver=2.6.2

Maybe my deletion request of z-push-git is premature

Interesting. A VCS pkgbuild is supposed to already grab the latest commit of a given branch, z-push-latest-git what exactly do? Note that -latest in pkgbuild have a very negative connotation, exist z-push branch called latest?

Aside from "$(git rev-list --count HEAD).$(git rev-parse --short HEAD)" from which template all the other code come from?

It’s funny that you’re asking for the meaning of all that code. And without understanding, you are asking for deletion of the other package.

This doesn’t feel right at all!

The pkgbuild file is the same, but depending on the name it behaves differently! All the functions make it way easier to maintain a standard behavior across all packages.

All code comes from a template, which people are encouraged to use by the arch wiki, also.

I'm not interested in using z-push, I care that AUR pkgbuild follow packaging guidelines.

Why there is stuff like "git clone --bare" and all that custom function and variables

Fabio, maybe this is the right package for you? (See the pinned comment)

https://aur.archlinux.org/packages/z-push-latest-git/

Hej Fabio,

I'm totaly with you!

This package has been the last package I've build for git and it's simply unfinished because I wanted to rework the package() part.

I'll make it git and leave the package part, so you could go with the latest commit.

Thanks for calling me up and explaining.

marti

Hello, the meaning of a -git (VCS) pkgbuild is to download the latest commit (not only using git for download), while this pkgbuild is cloning a fixed release, and I have seen you also uploaded a z-push-latest-git

https://wiki.archlinux.org/title/VCS_package_guidelines

What are you trying to say? Do you want me to figure out the release by the published tar.gz-file?

Tarball-Releases do exist only for older releases. So they won't create them after 2.3.

https://z-push.org/download/

"There aren’t tarball releases available for Z-Push 2.6!"

https://github.com/Z-Hub/Z-Push/tree/release/2.6

https://github.com/Z-Hub/Z-Push/tree/2.6.2

https://github.com/Z-Hub/Z-Push/releases

https://github.com/Z-Hub/Z-Push/releases/tag/2.6.2

https://z-push.org/z-push-2-6-2-final-released/

https://download.kopano.io/zhub/z-push%3A/final/Debian_10/

https://download.z-push.org/final/2.3/