public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Michal Schorm <mschorm@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/nemo] rawhide: Remove unnecessary '%ldconfig_scriptlets extensions'
Date: Sun, 26 Jul 2026 20:57:57 GMT [thread overview]
Message-ID: <178509947779.1.1877950933371975406.rpms-nemo-a01f7edfb1e4@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/nemo
Branch : rawhide
Commit : a01f7edfb1e4715afba3a18afe7c4c63aa273333
Author : Michal Schorm <mschorm@redhat.com>
Date : 2026-07-26T19:23:59+02:00
Stats : +0/-2 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/nemo/c/a01f7edfb1e4715afba3a18afe7c4c63aa273333?branch=rawhide
Log:
Remove unnecessary '%ldconfig_scriptlets extensions'
Since Fedora 28 (2018), RPM file triggers automatically run ldconfig
when shared libraries are installed or removed from standard library
directories. The explicit '%ldconfig_scriptlets' macro is redundant.
Reference: https://fedoraproject.org/wiki/Changes/RemoveObsoleteScriptlets
The nemo-extensions subpackage ships 'libnemo-extension.so.*' in
'%{_libdir}/' (a standard library path), so ldconfig is handled
automatically by file triggers.
The macro was added in commit 58b70f4 (2018-02-05, "update to git
snapshot") when the spec transitioned from explicit '%post -p
/sbin/ldconfig' to the '%ldconfig_scriptlets' macro. It was never
removed after file triggers made it unnecessary.
Co-Authored-By: Claude AI <noreply@anthropic.com>
---
diff --git a/nemo.spec b/nemo.spec
index 028c034..d94a6a8 100644
--- a/nemo.spec
+++ b/nemo.spec
@@ -126,8 +126,6 @@ mkdir -p %{buildroot}%{_libdir}/nemo/extensions-3.0/
rm %{buildroot}%{_datadir}/nemo/search-helpers/id3.nemo_search_helper
rm %{buildroot}%{_datadir}/nemo/search-helpers/pdf2txt.nemo_search_helper
-%ldconfig_scriptlets extensions
-
%files
%doc AUTHORS NEWS
%license COPYING COPYING-DOCS
reply other threads:[~2026-07-26 20:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178509947779.1.1877950933371975406.rpms-nemo-a01f7edfb1e4@fedoraproject.org \
--to=mschorm@redhat.com \
--cc=git-commits@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox