Bug 421460

Summary: kdeinit should not be in PATH
Product: [Frameworks and Libraries] frameworks-kinit Reporter: Christopher Yeleighton <giecrilj>
Component: generalAssignee: David Faure <faure>
Status: RESOLVED NOT A BUG    
Severity: minor CC: kdelibs-bugs, yurchor
Priority: NOR    
Version: 5.55.0   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Linux   
URL: https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.html#usrlibexec
Latest Commit: Version Fixed In:
Sentry Crash Report:
Bug Depends on: 324565    
Bug Blocks:    

Description Christopher Yeleighton 2020-05-13 12:50:17 UTC
SUMMARY

kdeinit should not be in PATH

STEPS TO REPRODUCE
1. { kdeinit5; }

OBSERVED RESULT


EXPECTED RESULT
Command not found.

SOFTWARE/OS VERSIONS
Windows: 10
macOS: 
Linux/KDE Plasma: 4.4.0-18362-Microsoft #836-Microsoft
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 5.55.0
Qt Version: 5.9.7

ADDITIONAL INFORMATION
Comment 1 Christopher Yeleighton 2020-05-13 12:52:19 UTC
Since it has been decided it is not a user command, it should be moved to libexec.
Comment 2 Christopher Yeleighton 2020-05-13 15:16:03 UTC
/usr/libexec includes internal binaries that are NOT INTENDED TO BE EXECUTED directly by users or shell scripts. Applications may use a single subdirectory under /usr/libexec.

Applications which use /usr/libexec in this way MUST NOT also use /usr/lib to store internal binaries, though they may use /usr/lib for the other purposes documented here.
Comment 3 Christopher Yeleighton 2020-05-13 15:30:58 UTC
Would you reconsider it as a feature request?
Comment 4 Yuri Chornoivan 2020-05-13 15:34:57 UTC
(In reply to Christopher Yeleighton from comment #3)
> Would you reconsider it as a feature request?

No. No bikeshedding, please. This saves no kitties and makes nobody happy.
Comment 5 Christopher Yeleighton 2020-05-13 15:40:30 UTC
(In reply to Yuri Chornoivan from comment #4)
> (In reply to Christopher Yeleighton from comment #3)
> > Would you reconsider it as a feature request?
> 
> No. No bikeshedding, please. This saves no kitties and makes nobody happy.

Manual page validation scripts may fail on a non-user-executable command installed in /usr/bin.  So you have one hypothetical kitty (and my actual motivation for reporting this).  Another solution would be to remove the manual page, but this would help genuinely nobody.