Created attachment 466396 [details] emerge --info conky Hello. conky-1.9.x used to install manpages. conky-1.10.4 doesn't. So now if I want to make slight adjustments to my conkyrc I need to go online and search for a list of available configuration options there. This is called a regression. $ equery f conky * Searching for conky ... * Contents of app-admin/conky-1.10.4: /usr /usr/bin /usr/bin/conky /usr/share /usr/share/doc /usr/share/doc/conky-1.10.4 /usr/share/doc/conky-1.10.4/AUTHORS.bz2 /usr/share/doc/conky-1.10.4/ChangeLog.bz2 /usr/share/doc/conky-1.10.4/NEWS.bz2 /usr/share/doc/conky-1.10.4/README.gentoo.bz2 /usr/share/doc/conky-1.10.4/README.md.bz2 /usr/share/doc/conky-1.10.4/TODO.bz2 /usr/share/doc/conky-1.10.4/conky.conf.bz2 /usr/share/doc/conky-1.10.4/conky_no_x11.conf.bz2 /usr/share/doc/conky-1.10.4/convert.lua.bz2 /usr/share/vim /usr/share/vim/vimfiles /usr/share/vim/vimfiles/ftdetect /usr/share/vim/vimfiles/ftdetect/conkyrc.vim /usr/share/vim/vimfiles/syntax /usr/share/vim/vimfiles/syntax/conkyrc.vim Please fix.
Call it whatever you like. Unfortunately not installing the man pages is a compromise between conky not being able to install at all or having a conky installation without man pages. If you can properly fix bug #486270 I will gladly enable the installation of the man pages again! *** This bug has been marked as a duplicate of bug 486270 ***
(In reply to Daniel Pielmeier from comment #1) > Call it whatever you like. Unfortunately not installing the man pages is a > compromise between conky not being able to install at all or having a conky > installation without man pages. > > If you can properly fix bug #486270 I will gladly enable the installation of > the man pages again! > > *** This bug has been marked as a duplicate of bug 486270 *** Ok, I've looked at the referenced bug and I've glanced through upstream build system. It looks like the obvious solution here would be to call conky/doc/docgen.sh script during compile phase and then doman the resulting file in install phase. Have you already considered this option?
(In reply to Coacher from comment #2) > Ok, I've looked at the referenced bug and I've glanced through upstream > build system. > > It looks like the obvious solution here would be to call conky/doc/docgen.sh > script during compile phase and then doman the resulting file in install > phase. > > Have you already considered this option? That would be an option. However now that you bring this up again I took another look at it. I am thinking of replacing the failing command "find_program(APP_MAN man)" by "set(APP_MAN $(which man) CACHE FILEPATH MAN_BINARY)" in cmake/ConkyPlatformChecks.cmake. This manually creates a cmake cache entry with the path to the man command.
(In reply to Daniel Pielmeier from comment #3) > (In reply to Coacher from comment #2) > > Ok, I've looked at the referenced bug and I've glanced through upstream > > build system. > > > > It looks like the obvious solution here would be to call conky/doc/docgen.sh > > script during compile phase and then doman the resulting file in install > > phase. > > > > Have you already considered this option? > > That would be an option. > > However now that you bring this up again I took another look at it. I am > thinking of replacing the failing command "find_program(APP_MAN man)" by > "set(APP_MAN $(which man) CACHE FILEPATH MAN_BINARY)" in > cmake/ConkyPlatformChecks.cmake. > > This manually creates a cmake cache entry with the path to the man command. This also looks like a viable solution to me. It's more elegant. Please do.
Fixed in Git. Thanks for the report.
