Package Details: cherrytree-git 1.1.2.r5.g4db6074c-1

Git Clone URL: https://aur.archlinux.org/cherrytree-git.git (read-only, click to copy)
Package Base: cherrytree-git
Description: Hierarchical note-taking application, git version
Upstream URL: https://github.com/giuspen/cherrytree
Licenses: GPL-3.0-or-later
Conflicts: cherrytree
Provides: cherrytree
Submitter: morgenstern
Maintainer: morgenstern
Last Packager: morgenstern
Votes: 9
Popularity: 0.001072
First Submitted: 2020-08-28 10:03 (UTC)
Last Updated: 2024-04-28 04:30 (UTC)

Latest Comments

« First ‹ Previous 1 2

furioness commented on 2022-06-07 10:26 (UTC) (edited on 2022-06-07 10:27 (UTC) by furioness)

@morgenstern I read that whole guideline. What I see is that it will get the latest version during installation. I can't see it saying that it will update AUR PKGBUILD.

The problem is how it will know that there is a newer version prior to installation by running something like pacman -Syu when PKGBUILD has not been changed (hence package databases).

Or maybe there is some step to check all locally installed packages that are VCS-based? I only can see the message Synchronising package databases, it doesn't sound like it would do something like that. Maybe because I used yay.

Just checked this article. It even suggests using some utils to be notified about new releases. Again, I don't see any automation in updating the version. https://wiki.archlinux.org/title/Arch_package_guidelines#Working_with_upstream

morgenstern commented on 2022-06-07 09:48 (UTC)

@furioness This package complies with the Arch VCS package guidelines and uses the pkgver() function to update pkgver when invoked by makepkg:

pkgver() {
  cd "${_pkgname}"
  git describe --long --tags | sed 's/\([^-]*-g\)/r\1/;s/-/./g'
}

furioness commented on 2022-06-07 09:02 (UTC) (edited on 2022-06-07 09:04 (UTC) by furioness)

I had ver 0.90.40 when the current is 0.90.47 or something like that. I tried to install cherrytree-git just to notice that I already had the git version (e.g. this one). Reinstalling do the deal, but this way denies the point of being under a package manager that keeps packages up to date. So, despite this one being git-based, it looks outdated to me.

I checked the first git-based package that got in my sight to see if it has the same problem. https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=scsi2sd-v6-git As you can see, it has pkgver variable, so the package manager can see that there is a newer version.

So, I suggest you add some kind of pkgver variable. Sorry if I misunderstand something. Thank you for maintaining.

hans commented on 2021-12-31 19:25 (UTC)

To my happy surprise this created automagically a newer version, 0.99.44 Thanks!

morgenstern commented on 2021-01-22 21:34 (UTC)

Tests are now built and run separately and are not optional.

If building in a clean chroot, see here and here for allowing chroot access to your X server.

morgenstern commented on 2021-01-02 22:56 (UTC)

Tests can now be run if desired - uncomment the check() function in the PKGBUILD and see the notes about allowing chroot access to your X server if relevant.

« First ‹ Previous 1 2