Tool for fetch logentries for Arch packages.
Find a file
2024-07-10 19:14:36 +02:00
.github Bump actions/setup-go from 4 to 5 2024-01-28 22:38:08 +01:00
pkg Slight restructuring 2023-10-03 18:13:20 +02:00
.editorconfig Initial project setup 2023-07-15 10:42:54 +02:00
.gitignore Ignore binary 2023-07-15 20:57:18 +02:00
build_man.sh Improve manpage generation. Move VERSION to dedicated file 2023-10-04 15:20:26 +02:00
go.mod Update dependencies 2024-07-10 19:14:36 +02:00
go.sum Update dependencies 2024-07-10 19:14:36 +02:00
LICENSE Create LICENSE 2023-07-16 16:31:28 +02:00
log.go Slight restructuring 2023-10-03 18:13:20 +02:00
main.go Improve manpage generation. Move VERSION to dedicated file 2023-10-04 15:20:26 +02:00
MANUAL.txt Add CONTACT to manpage 2024-07-10 19:11:50 +02:00
pkgbuild.go Slight restructuring 2023-10-03 18:13:20 +02:00
README.md Add info tp README 2023-10-03 15:59:55 +02:00
VERSION Improve manpage generation. Move VERSION to dedicated file 2023-10-04 15:20:26 +02:00

arch-log

arch-log is a small program that displays the commit messages or PKGBUILD of Arch packages. It queries both Arch's central repo and the AUR.

It is available on AUR: https://aur.archlinux.org/packages/arch-log

Rationale

If you have multiple custom packages in Arch, you know the drag: You notice that some package of which you have a custom fork (or just an AUR package with long compile time) has a new version -- but only the pkgrel has changed.

The question then is: Do I need to rebuild / rebase / ... or can I ignore the change. To make this decision, it is necessary to have the package's changelog in quick access.

As I'm tired of clicking through different web interfaces, and I don't know of any other tool that provides this: arch-log was born.

Additionally, while not really a log, it also has the capability of show the PKGBUILD of a package. Just for convenience's sake.

What does it do?

  1. Query https://archlinux.org/packages for the pkgbase.
  2. If found: Query https://gitlab.archlinux.org (using Gitlab's REST API) for the commit and tag data.
  3. Query https://aur.archlinux.org/rpc for pkgbase.
  4. If found: Query https://aur.archlinux.org/cgit/aur.git (using the Atom Feed) for the commit data.

What's with the name?

paclog was already taken.

How does it look like?

Default

Example

With repo information

This is shown, when Arch repos differ (e.g. there is a new version in testing)

Example Repo

Long

Example Long

Support

Thanks to JetBrains for supporting this project.

JetBrains