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.001368
First Submitted: 2020-08-28 10:03 (UTC)
Last Updated: 2024-04-28 04:30 (UTC)

Latest Comments

1 2 Next › Last »

morgenstern commented on 2025-06-01 05:52 (UTC)

Thanks @waitnsea - I had noticed that bug recently, but just assumed it was something weird I was copying and pasting!

waitnsea commented on 2025-06-01 02:53 (UTC)

a bug fixed https://github.com/giuspen/cherrytree/issues/2705

waitnsea commented on 2024-07-07 17:13 (UTC)

@morgenstern sorry . Thanks

morgenstern commented on 2024-07-07 13:07 (UTC)

@waitnsea please see the comment history - this has been discussed multiple times (here, here, and in the most recent comment below yours here).

waitnsea commented on 2024-07-07 12:47 (UTC)

out-of-date but PKGBUILD works always well, simply moving version to 1.1.4

morgenstern commented on 2022-06-29 15:37 (UTC)

@Chinaboy5216 do not mark VCS packages as out of date.

furioness commented on 2022-06-07 11:00 (UTC) (edited on 2022-06-07 11:03 (UTC) by furioness)

I found this topic https://www.reddit.com/r/archlinux/comments/a030v7/how_do_you_manage_git_aur_packages/ Seems like people do in a way similar to described by you.

We've posted simultaneously. I accept your answer then. Thank you for your time. I hope it's ok to have this slightly offtopic here.

morgenstern commented on 2022-06-07 11:00 (UTC)

The rationale is that VCS AUR packages would constantly need their PKGBUILDs updated, which would be a waste of time and would also overwhelm aurweb. Although this is not explicitly stated, this section of the Arch User Repository wiki page indicates that AUR maintainers of VCS packages should not commit mere pkgver bumps.

Therefore, the onus is on end-users to check for updates to VCS AUR packages and re-run makepkg as they see fit. There are dozens of different tools available for tracking updates - pacvcs is one that is specific to VCS packages in the AUR, but if you were looking for a more popular choice, then I would look into nvchecker.

furioness commented on 2022-06-07 10:52 (UTC) (edited on 2022-06-07 10:54 (UTC) by furioness)

@morgenstern At least it seems that I understand this versioning machinery correctly.

Sorry to keep bothering you, but could you link me some info about an agreement on this approach where maintaining VCS-based package updates is the end-user's responsibility, it feels counter-intuitive to me.

From another point of view, having to update the git version manually allows the package maintainer to assure that the update breaks nothing. So each maintainer does his little part. Otherwise, the burden of tens or hundreds of packages validity check drops on a single end-user. Also, it may slow down the update process (in theory).

And https://aur.archlinux.org/packages/pacvcs seems to have stunningly low popularity for such a seemingly important package (if your ideology (if I understand it correctly) is supported by the community).

Probably will ask for opinions on this topic on IRC later.

morgenstern commented on 2022-06-07 10:30 (UTC)

You will need to check if there are new commits and then rebuild the package if desired. Personally, I use the AUR packages pacvcs in a pacman hook so that I can see which VCS AUR packages need updating when I run pacman -Syu.

1 2 Next › Last »