README: document the AUR packages - #27
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi, @tobi!
disktree is exactly what I look for in a disk usage tool, and being made for Omarchy it fits my desktop perfectly, so I packaged it for the AUR. This PR adds it to the README (change or drop the wording if you would rather keep
the install section as is).
There are two packages:
disktreebuilds each release from the tagged source tarball withcargo build --lockeddisktree-bininstalls the official release binary (x86_64 and aarch64) — the same three filesmake installwould put under~/.local, just system-wideBoth stay current on their own. aur-disktree checks this repo's releases hourly and, on a new tag, bumps
pkgver, pulls the checksums from your.sha256assets, regenerates.SRCINFOand pushes both package bases. It is currently sitting at 0.10.0 and should pick up 0.10.1 within the hour.Last thing: if you would rather control the AUR releases yourself, it is all yours. I can add you as co-maintainer on both package bases (or transfer them outright, whatever you prefer), and the sync repo can move under your account, where it could be driven by your release workflow directly instead of polling. Just say the word.