Bug 1380291

Summary: tcl manpages should ideally be in a separate package
Product: [Fedora] Fedora Reporter: Tor Lillqvist <tml>
Component: tclAssignee: Jaroslav Škarvada <jskarvad>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: rawhideCC: jskarvad, wart
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tcl-8.6.6-2.fc26 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-29 10:18:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Tor Lillqvist 2016-09-29 08:29:34 UTC
Description of problem:

It's slightly annoying that the tcl manpages are so numerous and have so generic title lines that they make it much harder to find what you are looking for with 'man -k'. Whatever you look for, you typically have to skip dozens of tcl manpages when browsing the output. I assume very few people are actually writing software in Tcl/Tk these days, and need those manpages.

Comment 1 Tor Lillqvist 2016-09-29 08:58:38 UTC
OK, my friendly neighbour Fedora expert tells me to do:

dnf reinstall tcl --setopt='tsflags=nodocs'

so I'll close this bug myself then;) I guess another question is why tcl got installed in the first place, no idea if that is the default for development systems, or might have been my own fault after installing something obscure I don't use anyway, or whatever...

Comment 2 Jaroslav Škarvada 2016-09-29 09:26:07 UTC
(In reply to Tor Lillqvist from comment #1)
> OK, my friendly neighbour Fedora expert tells me to do:
> 
> dnf reinstall tcl --setopt='tsflags=nodocs'
> 
> so I'll close this bug myself then;) I guess another question is why tcl got
> installed in the first place, no idea if that is the default for development
> systems, or might have been my own fault after installing something obscure
> I don't use anyway, or whatever...

Thanks for the report, the above is dirty workaround. I think it makes sense to have the docs in separate package, thus reopening but against rawhide.