Just for illustration, this might be the change you want to apply to
your plugin:
```
$ git diff
diff --git a/vim-commentary.spec b/vim-commentary.spec
index 4f75a8f..c275cc3 100644
--- a/vim-commentary.spec
+++ b/vim-commentary.spec
@@ -46,13 +46,6 @@ install -m 644 %{SOURCE1} %{buildroot}%{appdata_dir}
# Check the AppData add-on to comply with guidelines.
appstream-util validate-relax --nonet
%{buildroot}/%{_datadir}/appdata/*.metainfo.xml
-%post
-vim -c ":helptags %{vimfiles_root}/doc" -c :q &> /dev/null
-
-%postun
-> %{vimfiles_root}/doc/tags
-vim -c ":helptags %{vimfiles_root}/doc" -c :q &> /dev/null
-
%files
%doc CONTRIBUTING.markdown README.markdown
%{vimfiles_root}/doc/*
```
Vít
Dne 8.11.2016 v 09:27 Vít Ondruch napsal(a):
> Hi,
>
> Just a short note to all vim plugins maintainers. Yesterday, I added
> %transfiletriggerin and %transfiletriggerpostun triggers into vim
> package [1, 2], therefore you can safely remove your %post{,un}
> scriptlets, which you used to refresh the documentation. This should be
> done automatically now.
>
>
> Vít
>
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1343357
>
> [2]
> http://pkgs.fedoraproject.org/cgit/rpms/vim.git/commit/?id=d76e3c95ac644b1ab577bf4db79fb055f218724d
>
> _______________________________________________
> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
