Arch Linux User Repository

Hey @lime, I understand exactly what you're saying. Please become familiar with the AUR submission guidelines and rules (https://wiki.archlinux.org/title/AUR_submission_guidelines), specifically this one:

• Packages that build from a version control system and are not tied to a specific version need to have an appropriate suffix, -git for git and so on, see VCS package guidelines#Package naming for a full list.

which is exactly the case here. Note, while typically -git packages are used to denote the latest commit (on some dev branch), that is not what the -git suffix means. It simply means that the package is NOT tied to a specific version (and is built from source).

Hence, removing the -git suffix here would be in breach of AUR submission rules.

It's up to the maintainer to choose which branch to build off (and the intent was to build release branch in this case).

Finally, I was maintaining these AUR packages for a while but have stopped actively doing so (except for this -git package which will always build the latest release). The recommended way of installing PaperWM now is from gnome extensions or diretly from source (which aligns with this AUR package): https://github.com/paperwm/PaperWM?tab=readme-ov-file#installation, as outlined in the README).

Jay.

@j.taala I understand, but what I'm saying is that this package should be renamed to drop the -git suffix (even if it happens to be downloaded from github). -git indicates a package tracks the last git commit (even if it hasn't been tagged as a release), not the latest release version.

Hey Lime. No, the intent of this package to is to the latest release as we are no longer maintaining AUR packages (e.g. no longer producing or maintaining gnome-shell-extension-paperwm whenever we release).

Hi @j.taala @hikhvar — I think there's a minor error in packaging here. -git packages are supposed to install the latest development version/latest commit (i.e. on the develop branch), rather than the latest version on the release branch. Released versions should be installed by a package called gnome-shell-extension-paperwm instead.

P.S. I like @xeyler's suggestions here - makes it much nicer. Planning in incorporating them here, mayber after we get #531 and #535 in?

Happy to not add .git folder - good suggestion.

For versions, the main reason was basically we haven't used/updated tags (and done releases) for a long time. Have now started that again, so potentially moving to tags based describe makes sense.

Thoughts @hikhvar?

Is there any reason to include the .git* folders/files into the package? Adding -not -path '*.git*' to the find on line 24 excludes them.

Why not version the package as recommended by Arch VCS package guidlines? See: https://wiki.archlinux.org/title/VCS_package_guidelines#Git:~:text=Using%20the%20most%20recent%20un%2Dannotated%20tag%20reachable%20from%20the%20last%20commit%3A

diff --git a/PKGBUILD b/PKGBUILD
index 5eb255f..98bc0e6 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,7 +1,7 @@
 # Maintainer: Christoph Petrausch aur@petrausch.info
 pkgname=gnome-shell-extension-paperwm-git
 _pkgname=PaperWM
-pkgver=r1953.0592c92
+pkgver=v44.0.1.r0.g0592c92
 pkgrel=1
 pkgdesc="A gnome shell extension providing scrollable tiling of windows and per monitor workspaces."
 arch=('any')
@@ -14,7 +14,7 @@ md5sums=('SKIP')

 pkgver() {
   cd "$srcdir/$_pkgname"
-  printf "r%s.%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)"
+  git describe --long --tags --abbrev=7 | sed 's/\([^-]*-g\)/r\1/;s/-/./g'
 }

 package() {

Thanks @hikhvar! Yes, I agree re PaperWM - I also wouldn't be without it (everything else feels unnatural now). Re the GitHub actions - that sounds awesome and definitely something to look at moving forward.

Hey,

thanks for the great work on PaperWM. That is my daily driver and I think I couldn't live without it anymore. I have added you as a co-maintainer. Maybe we could setup some automatic release workflow via GitHub Actions, so none of us has to do manual work?