From c48e554712b837a5c9608bab4448fe790b9459e8 Mon Sep 17 00:00:00 2001 From: Josephine Pfeiffer Date: Thu, 14 May 2026 17:14:33 +0200 Subject: [PATCH] docs(man): cross-reference IgnoreDevelSource from --devel The --devel section explains the git ls-remote mechanism but never names the failure modes it has: PKGBUILDs that check out a different ref in prepare(), or list git sources that don't drive pkgver, will appear as devel updates on every run even though the resulting package is identical. Users repeatedly file this as a bug instead of reaching for the existing IgnoreDevel / IgnoreDevelSource knobs in paru.conf(5). Add a paragraph pointing at both options so the escape hatch is discoverable from the place readers actually look. Signed-off-by: Josephine Pfeiffer --- man/paru.8 | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/man/paru.8 b/man/paru.8 index cddaa8ea..c2cdfce0 100644 --- a/man/paru.8 +++ b/man/paru.8 @@ -530,6 +530,12 @@ checked almost instantly and not require the original PKGBUILD to be downloaded. The slower pacaur-like devel checks can be implemented manually by piping a list of packages into paru (see \fBexamples\fR). +Some packages track git sources whose HEAD moves often without changing the +resulting package version. These will appear as devel updates on every run even +when rebuilding produces an identical package. See \fBIgnoreDevel\fR and +\fBIgnoreDevelSource\fR in \fBparu.conf\fR(5) to opt such packages or sources +out of devel checking. + .TP .B \-\-ignoredevel Like --ignore but for devel upgrades. Packages matching this will not be tried for a