-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Wed, 2018-01-03 at 16:53 +0100, Tomasz Kłoczko wrote: > Hi, > > I'm trying to follow procedure described on > https://fedoraproject.org/wiki/Mass_package_changes > > Description of the current state > ======================= > > At the moment more than many spec files have %post/%postu/%postrans > scriptles in which is done updating hicolor theme cache by calling: > > gtk-update-icon-cache -f %{_datadir}/icons/hicolor > > All those scriptles are no longer needed because in hicolor-icon-theme > package has file triggers updating theme cache on any change in single > dnf/rpm transaction. > > $ rpm -q --filetriggers hicolor-icon-theme > transfiletriggerin scriptlet (using /bin/sh) -- /usr/share/icons/hicolor > gtk-update-icon-cache --force /usr/share/icons/hicolor &>/dev/null || : > transfiletriggerpostun scriptlet (using /bin/sh) -- /usr/share/icons/hicolor > gtk-update-icon-cache --force /usr/share/icons/hicolor &>/dev/null || : > > Remove all those %post/%postu/%postrans scriptles will speedup install > and upgrades as only one time gtk-update-icon-cache will be executed > as hicolor-icon-theme transaction action. > > List of affected packages > =================== > On the list is more than 1300 packages. > List has been generated in directory with all spec files extracted > from git repos using command: > > $ grep 'gtk-update-icon-cache.*hicolor' * | grep -v hicolor-icon-theme > > awk -F\. '{print $1}' | uniq > gtk-update-icon-cache_hicolor.lst > > gtk-update-icon-cache_hicolor.lst has been added as the attachment in > this email. > > > If it will be no more comments about this proposal I'll try in a week > follow next steps of the procedure described on Fedora wiki sending > final proposal to devel-announce list and after this raise ticket in > BTS. > > PS. Please advise how to implement change without raising +1300 > tickets on bugzilla (I'm not going to sped weeks or months on > introduce such simple change) First thing you should do is to open a ticket for FPC[0] in order to fix guidelines. Once it is approved by FPC, I can help you dealing with this as a proven packager since it is trivial enough. [0] https://pagure.io/packaging-committee - -- - -Igor Gnatenko -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEhLFO09aHZVqO+CM6aVcUvRu8X0wFAlpNAC8ACgkQaVcUvRu8 X0w27A//dbQxuRtpHRMaM090WVRz7fyvXLAbDXN42/Au8OgmKuB4tHrF0lH09GN4 XnW8dBjJDMkRRTjeQ1Hofj6Iq1h+dWRcpc+jXSzaRtBdojT64mAotQD0j2ScmqWo hsu9nMNhsQYaAJJb68O8jRy8K7+kN2e+MS0jYEMOR2nubUr/pPd/AMs1170kgddG S59lwpZB3zdJlsyIcCbRTk54Ls/rB84nAz+8bJi32qxRPVZxcOY/AtIQowx8GxNE bC8kqYV8zrI7gQNScg1mrjkCBZDWXAVZ/pz/3Bckv55TchzIof8/Q6fIzc6KVblv j5dWx8KqiBbDhrAPWlo6d+m29KVbjWO5T3Kv1348yLh4W74ZNDlVsiCWtyVIYiIj ukDJMAy4Y84z72A0l/DC8HRbV2rJOWkw2F/NVVeZbvphP/tfkAM7n+ra6EaUuMe9 /LU8vMq6zJpDsokpeBnuP6rdg9KB2DYKCUVT/H0eTvvkOq7Z0xSFbkQobDR/D62n yu2hg5zzXwS0qRgLYqpOIOXyLxHLbeG6N54VohuSPGDf/Pq2Y/w+W/5tolY5SrIW U1ltvAVHZ1CvKJeTA3kiVGSU8ej62XbXKd+impcfxgkJSixNBANoyr3abp7LdhG+ Gbd/HDpJCC6gIPLXmhejQKoImlT0qax98+pHe9araMqt/HFqLZ8= =/ELg -----END PGP SIGNATURE----- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
