Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use dpkg triggers instead of manual update-desktop-database/update-mime-database calls #1928

Open
legoktm opened this issue Mar 18, 2024 · 0 comments

Comments

@legoktm
Copy link
Member

legoktm commented Mar 18, 2024

Description

https://wiki.debian.org/DpkgTriggers are a more declarative way to have certain post-processing run after package install. Both update-desktop-database and update-mime-database have supported triggers since way before bullseye.

In theory we'd be able to get rid of all of:

user@dev ~/g/f/securedrop-client (main)> rg 'update-(desktop|mime)-database'
debian/securedrop-client.postinst
24:    update-desktop-database /usr/share/applications
29:    update-desktop-database /usr/share/applications

debian/securedrop-export.postinst
25:    update-desktop-database /usr/share/applications
26:    update-mime-database /usr/share/mime
36:    update-desktop-database /usr/share/applications
37:    update-mime-database /usr/share/mime

debian/securedrop-export.postrm
27:    if [[ -x "/usr/bin/update-desktop-database" ]]; then
28:        update-desktop-database /usr/share/applications
30:    if [[ -x "/usr/bin/update-mime-database" ]]; then
31:        update-mime-database /usr/share/mime
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant