Bug 1343357 - Use transaction triggers to refresh documentation.
Summary: Use transaction triggers to refresh documentation.
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: vim
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Vít Ondruch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1284645
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-07 08:17 UTC by Vít Ondruch
Modified: 2016-11-07 15:56 UTC (History)
3 users (show)

Fixed In Version: vim-8.0.037-2.fc26
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-07 15:56:47 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
RPM file triggers support (1.44 KB, patch)
2016-06-07 08:17 UTC, Vít Ondruch 		no flags Details | Diff
View All

Description Vít Ondruch 2016-06-07 08:17:16 UTC 
Created attachment 1165522 [details]
RPM file triggers support

Description of problem:
Currently, all vim plugins need to contain lines such as [1]:

%post
vim -c ":helptags %{vimfiles}/doc" -c :q &> /dev/null

%postun
> %{vimfiles}/doc/tags
vim -c ":helptags %{vimfiles}/doc" -c :q &> /dev/null

to refresh the documentation index. It would be nice, if this is handled in vim package via transaction triggers [2].




[1] http://pkgs.fedoraproject.org/cgit/rpms/vim-commentary.git/tree/vim-commentary.spec?id=1cf2381a567e893ec4fe6d1f659d93d75a5dde58#n51
[2] http://www.rpm.org/wiki/FileTriggers
Comment 1 Igor Gnatenko 2016-07-07 07:28:53 UTC 
Agree, would be nice to have.
Comment 2 Jan Kurik 2016-07-26 04:29:33 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.
Comment 3 Igor Gnatenko 2016-09-14 08:12:31 UTC 
ping?
Comment 4 Karsten Hopp 2016-10-04 09:26:50 UTC 
I'm back from PTO now but don't have time to have a look at this atm. Please feel free to add those triggers to vim
Comment 5 Vít Ondruch 2016-11-07 15:56:47 UTC 
Since the bug 1284645 got fixed, I took the liberty to implement this.
Note You need to log in before you can comment on or make changes to this bug.